Why new package name libsasl2-2

[Andreas Metzler]

On 2006-10-16 Fabian Fagerholm <fabbe at paniq.net> wrote:
> On Sun, 2006-10-15 at 14:41 -0400, Roberto C. Sanchez wrote:
>> On Sun, Oct 15, 2006 at 01:42:22PM -0400, Roberto C. Sanchez wrote:
>>> On Sun, Oct 15, 2006 at 07:39:35PM +0200, Sven Mueller wrote:
>>>> Andreas Metzler schrieb:
>>>>> #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. 

[...]
> Are you guys paying attention? :)

> Read policy, the library packaging guide and the posts sent to this list
> when I started this thing.

> Back when cyrus-sasl2 was first packaged, it was loosely modeled on the
> ancient cyrus-sasl (1.5.x) package. In those days, library packaging was
> much more ad-hoc than it is now. These days, people have accumulated
> more experience and this has been documented in the library packaging
> guide.
[...]
> So the reason for the name change includes these points:
>       * Be policy-compliant.
>       * Follow the library packaging guide.
>       * Don't allow choices made in the old package to unnecessarily
>         influence the new package. 
>       * Allow coexistence in the archive with cyrus-sasl2 (though not
>         coexistence in the same installation).

> So please, please, please, go back and read what I have written on this
> list *before* banging your head against the same issues.

Hello,
The package name is no "hard" policy requirement. OTOH, this is _critical_:
----------------------
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.
----------------------

I cannot see a real way to have both:
- Allow coexistence in the archive with cyrus-sasl2
and
- a upgrade scenario.

both are important, but the latter is more so.

You could start the way you did and later build a dummy libsasl2
package from cyrus-sasl-2.1 that just depends on libsasl2-2 package.
This would allow kind of a slow transition, but the conflict between
libsasl2-2 and the old libsasl2 takes any benefit awy from that
scenario. - The archive will be split in two halves that are not
concurrently installable, which will wreak havoc anyway.

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