bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Unifiying porting guidelines


From: Guillem Jover
Subject: Unifiying porting guidelines
Date: Mon, 23 May 2011 20:13:34 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

Hi!

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
<http://www.freedesktop.org/wiki/Software/Porting>.

For Debian specific issues the Debian wiki would be ideal, there's
already a skeleton at <http://wiki.debian.org/GettingPorted>.

For ArchHurd there's <http://wiki.archhurd.org/wiki/Porting_Guide>.

I've started working on this as I had an old portig doc around
<http://www.hadrons.org/~guillem/debian/ports/porting>, and if people
agree I'll just use it as the base, and then we can start merging
and splitting the rest.

  <http://glibc-bsd.alioth.debian.org/porting/PORTING>
  <http://www.gnu.org/software/hurd/hurd/porting/guidelines.html>
  <http://www.gnu.org/software/hurd/hurd/porting/system_api_limitations.html>
  <http://lists.debian.org/debian-hurd/2007/07/msg00001.html>

Probably not everything should be moved though, and things that
ressemble proper documentation of interfaces and similar should remain
in places like the Hurd wiki, the FreeBSD handbook, specific man
pages, etc, and just links to those be used.

regards,
guillem



reply via email to

[Prev in Thread] Current Thread [Next in Thread]