Why new package name libsasl2-2

Fabian Fagerholm fabbe at paniq.net
Tue Oct 17 06:38:52 UTC 2006


On Mon, 2006-10-16 at 19:09 +0200, Andreas Metzler wrote:
> 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.

Could you think of an upgrade scenario that involves changes to
cyrus-sasl2 (the old package) to prepare for cyrus-sasl-2.1? For
example, make cyrus-sasl2 produce a dummy libsasl2 which depends on, but
does not conflict with, libsasl2-2, which has a versioned conflict with
the non-dummy libsasl2's. This would make them concurrently installable,
right? During a slow transition we could then gradually drop the old
package.

Anyway, I don't think the package name is the most important thing right
now, since there is so much left to do on the package itself.

Cheers,
-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061017/5994ff20/attachment.pgp


More information about the Pkg-cyrus-sasl2-debian-devel mailing list