This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Don't document upgrading from libc5 (bug 5993)
- From: David Miller <davem at davemloft dot net>
- To: joseph at codesourcery dot com
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 17 Feb 2012 15:18:16 -0500 (EST)
- Subject: Re: Don't document upgrading from libc5 (bug 5993)
- References: <Pine.LNX.4.64.1202171646210.8905@digraph.polyomino.org.uk>
From: "Joseph S. Myers" <joseph@codesourcery.com>
Date: Fri, 17 Feb 2012 16:47:17 +0000 (UTC)
> Bug 5993 reports a broken link relating to upgrading from libc5.
> Information about upgrading from libc5 is long obsolete; support for
> libc5 was obsoleted in GCC long ago (though it took a while to get rid
> of various non-obvious relics). I think this information which was
> relevant 15 years ago is now just confusing and should be removed;
> this patch removes it. Since "make install" may not always remove old
> headers (I don't think we did anything to make it remove RPC headers,
> for example) I added a mention of that, but I think for any recent
> upgrades non-removal of old headers is fairly harmless. (Even the
> information about swapping out header directories is of doubtful
> relevance now. glibc really is targetted at various forms of
> distributors and package managers that will track automatically what
> was installed by the old version and deal themselves with removing old
> files.)
>
> Comments?
No objections from me, this probably should have been killed years
ago.