Re: Once again: libc6 packages compatibility etc...
> > The more this goes on, the more I think the best thing to do would have
> > been to just clean out hamm completely and only let libc6 packages
> > be uploaded.
> >
> > We could still do this, I suppose with very little impact on hamm.
> > The big problem is with upgrades from earlier versions.
>
> But we want to support people using old libc5-based programs (think
> about those using commercial software), so libc5-based libs are still
> needed. The way we are doing it now with both libc5- and libc6-based
> libs coexisting in the same system looks like the Right Thing to me.
That's why it's a problem with upgrades.
What I'm wondering is if there is a better way. One that doesn't cause
as many problems as this silly "g" suffix stuff.
The libc4 -> libc5 didn't have this bad a transition.
Brian
( bcwhite@verisim.com )
-------------------------------------------------------------------------------
Management should work for the engineers, not the other way around.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: