Hi, On Sat, Jun 02, 2012 at 09:53:39PM +0200, Ondřej Surý wrote: > that wouldn't be necessary in the future as there will be only one X.Y-dev > in the future (with the exception of transitions). Also you shouldn't (with > the > exception of some special cases) depend on libdbX.Y-dev, but just libdb-dev.
I don't - Python2.6, which is not managed by me, does. It even has a changelog entry mentioning that it now requires an *older* version of libdb. I don't dare to touch that dial... > Last but not least the berkeley db is fragile as is it (it's not > uncommon for app > to use one header X.Y, but link with different libdbX.Z which doesn't match > the header version), I also see some merit to support different versions of something, so one package could - in theory - work on several target platforms, but I realize that this is hard to achieve. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
