This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What is glibc-ports?
On Thu, 19 Apr 2012, Andreas Schwab wrote:
> "Joseph S. Myers" <joseph@codesourcery.com> writes:
>
> > In summary: I think libc architectures should use sysdeps directories more
> > rather than conditionals in generic code; ports architectures should move
> > back in libc architectures directly in the normal sysdeps directories
> > rather than in a ports/ subdirectory (though I don't object to temporary
> > use of such a subdirectory in the course of a move as a way of reading in
> > the history through git tricks before the files are moved);
>
> For the purpose of managing history it is better not to prepend
> ports/, because that avoids having to rename files.
Overlaps in filenames between libc and ports may mean it's problematic
just to read in the history without using a subdirectory, however, and the
directory structures in ports are different regarding where NPTL files go.
--
Joseph S. Myers
joseph@codesourcery.com