2008/1/13, Florian Weimer <[EMAIL PROTECTED]>:
> > Is there a good reason not to continue the scheme used in
> > libdb4.[12345] ?
>
> The name scheme is not the problem, it's the fact that all Berkeley DB
> -dev packages conflict (because they all install the db.h header file).
the db.h conflict is not the problem; that just means you can only
install one of libdb[12345]-dev, which provided virtual package
libdb-dev. That caused no problems.
Now in the Packages file instead of
Package: libdb4.4-dev
Provides: libdb-dev
Conflicts: libdb-dev, libdb1-dev, libdb2-dev, libdb3-dev
from version 4.6 we have
Package: libdb-dev
Provides: libdb4.6-dev
Conflicts: libdb1-dev, libdb2-dev, libdb3-dev
so a virtual package has become a real package (and libdb4.6-dev is virtual).
> Can't you link Subversion against Berkeley DB 4.6? According to a
> report on the Subversion mailing list, the current version passes its
> test suite unchanged even when using Berkeley DB.
I could if I were building for myself, but in the debian context
packages may build-depend on specific versions of libdb4.?-dev or may
be happy with any (specifying libdb-dev), some figures for how many
source packages specify the different versions in sid:
libdb4.1-dev 0
libdb4.2-dev 10
libdb4.3-dev 14
libdb4.4-dev 19
libdb4.5-dev 14
libdb4.6-dev 9
libdb-dev 38
Previously, the specific version would provide the virtual package
and both build dependencies would be satisfied. Now libdb-dev, which
should mean "any", always resolves to 4.6, which conflicts with the
specific version asked for by some other package.
The same build problem now occurs with php5:
.../php5-5.2.4# dpkg-checkbuilddeps
dpkg-checkbuilddeps: Unmet build dependencies: apache2-prefork-dev (>= 2.0.53-3)
.../php5-5.2.4# apt-get install apache2-prefork-dev
The following extra packages will be installed:
libaprutil1-dev libdb-dev
The following packages will be REMOVED:
libdb4.4-dev
.../php5-5.2.4# dpkg-checkbuilddeps
dpkg-checkbuilddeps: Unmet build dependencies: libdb4.4-dev
.../php5-5.2.4# apt-get install libdb4.4-dev
The following packages will be REMOVED:
apache2-prefork-dev libaprutil1-dev libdb-dev
... and so on.
What is the advantage of switching the virtual/real package names over?
To force the other 60 packages to make sure they work with libdb4.6
instead of having up to five versions if libdb installed on every
system? If it's worth the aggro, I agree it would be a step forward.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
