On Sun, Aug 18, 2002 at 05:36:04PM +0200, Luca Barbieri wrote: > > No because it is overcomplicated > This isn't a problem for you, I'm doing the work (I have already managed > to write a program to detect the ABI, a wrapper generator and patched > dpkg to move libraries; I still have to do shlibs support and hook the > wrapper generator to dpkg). > If it isn't accepted, I'll just further patch dpkg and apt to ignore the > bogus conflicts that would be added and use it locally. Complexity is directly proportional to bug frequency. It's a problem for all of us when unnecessarily complex kluges are added to dpkg. > > and dpkg has no business making this kind > > of on-the-fly adjustment. > Of course it would be better to avoid having to do things like this but > unfortunately there is simply no other solution that doesn't break > existing G++ v2 packages. Of course there is. You upload new versions of the gcc 2.95 packages, and you make the new gcc 3.2 packages conflict with the old ones. Nothing is broken in that case. Steve Langasek postmodern programmer
Attachment:
pgpitWlk1IedT.pgp
Description: PGP signature