Re: Unifiying porting guidelines
On Mon, May 23, 2011 at 08:13:34PM +0200, Guillem Jover wrote:
> We have several porting guidelines with sometimes similar or duplicate
> information. We were discussing this the other day on the #hurd IRC
> channel, and I think, and people seemed to agree there, that to help
> the majority of upstreams interested in portability, and to counter
> the vocal minority which seem to consider portability a thing of the
> past and are trying to push that idea and code into the rest of the
> system stack in detriment of the rest of the operating systems, it
> would be optimal to unify the information in a single place for
> upstreams and a single place for each distribution specific stuff.
> For upstream related content a neutral place like FreeDesktop's wiki,
> would be desirable, so that other distributions/upstreams can get
> easily involved and feel welcome, maybe something like
While countering the "fuck portability" trolls is certainly a noble
goal, I'm not sure a unified porting guide would be a good idea...
People usually look into portability issues in the context of a specific
system they want to port the package in question to.
Also, the Hurd at least needs some specific workarounds that do not have
much to do with portability in general; so a unified document wouldn't
really work well anyways...
Thus I'd prefer keeping all relevant Hurd porting information in the
Hurd wiki, and likewise for BSD.
This also avoids the need for getting another wiki login, thus lowering
the barriers to contribution...