Why new package name libsasl2-2
Andreas Metzler
ametzler at downhill.at.eu.org
Sun Oct 15 17:15:27 UTC 2006
Hello,
thanks to you all for investing time and energy to kick sasl in shape.
I have eyed SVN and came up with a couple of observations which you
either might not like and/or will show that I am not very familiar
with libsasl.
#1 The library package name has changed from libsasl2-2 to libsasl2. I
cannot see a reason for that, the soname is the same one as
previously. The new package introduces versioned symbols, but these
should only break backwards compatibilty, i.e. stuff built against
nonversioned will work with the new library but not the other way
round.
As libsasl2-2 and the old libsasl2 (need to) conflict with each other
this is going to make upgrades next to impossible. - It will be
impossible to install packages built against the old sasl and packages
built against the new sasl at the same time. apt currently requires sasl
(By apt -> debian-archive-keyring -> gnupg -> libldap2 dependency
chain) so the new sasl is practically uninstallable.
Compared to this a minor issue but still important:
(SID)ametzler at argenau:$ grep-available -FDepends -sPackage libsasl2 |\
grep -v sasl | wc
68 136 1632
You would need to have almost 70 packages be ready for testing migration
at the same time. (BinNMUs might make this doable, actually)
cu andreas
--
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken. (c) Jasper Ffforde
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061015/3e9bb879/attachment.pgp
More information about the Pkg-cyrus-sasl2-debian-devel
mailing list