The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Which libc should we use in the future?

On Thu, 10 Oct 1996, Brian C. White wrote:

> [...]
> This will work, but only with minor revisions to the library.  Major
> revisions (hence the change of the first number of the version) usually
> mean a significantly different interface and thus cannot be a "drop in"
> replacement.  "libc5" could not be a drop-in replacement for "libc4"
> because the former was ELF and the latter was A.OUT.  There may have
> been other changes, too, though.
> 
> However, there is no reason why we can't have libc4, libc5, and libc6 all
> exist together and an executable just uses whichever it was originally
> linked against.  Usually you can only have one "libc-dev" package, though,
> and so packages will progress towards the latest as time marches on.

Yes, I appreciate all that.  However, had I not been told otherwise, I
would have expected to be able to upgrade from libc5.xx to libc5.yy
(yy>xx) and still be able to build things to run on libc5.xx platforms ...

Nikhil.

--
Nikhil Nair
Trinity College, Cambridge, England
Tel.: +44 1223 368353
Email: nn201@cus.cam.ac.uk
       nnair@debian.org



--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com