This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: example add-on ports of glibc


Thanks for all the work on this, Alex.

Alex has provided the first add-on port in the new contributed ports
repository.  You can now see in his am33 port the few tiny additions
necessary vs incorporating a new port's files into the main source tree.
If you have done a port already by adding sysdeps directories to your glibc
source tree and you have done your port cleanly, then there is very little
work involved in moving all your new files into a separate add-on port.

sysdeps/CPU/preconfigure (usually from sysdeps/CPU/preconfigure.in) is only
required if the CPU part of the tuple from config.sub can be other than the
exact name you've used for the sysdeps/CPU directories.  You can add
sysdeps/CPU/shlib-versions if your port should use DSO names or symbol
version sets other than the defaults in the main shlib-versions file.

Alex has set a fine precedent by maintaining a ChangeLog.am33 in canonical
GNU format.  There is already ports/ChangeLog that logs changes to the
shared infrastructure files (i.e. ports/configure.in) that every add-on
containing one or more ports will use.  The idea of the ports repository is
that the additions for a particular port can always be taken alone, with
just the few top-level files to make an individual add-on for a port that
works just like the canonical "ports" add-on maintained in this communal
repository.  In keeping with that, each port's own changes should be logged
in a ChangeLog.PORTNAME file for that port, strictly maintaining the same
conventions we use for ChangeLogs in the main glibc source tree.  If you
are maintaining and distributing your own add-ons for your ports
separately, how you do that is up to you.  But to share use of the
community ports repository, we're going to insist that you observe these
conventions for the benefit of everyone trying to read the sources.


Thanks,
Roland


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]