Why new package name libsasl2-2

[Roberto C. Sanchez]

On Tue, Oct 17, 2006 at 09:38:52AM +0300, Fabian Fagerholm wrote:
> 
> 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.
> 
I was thinking about this as a possibility.  However, if we create a
dummy package, then you end up with one empty package which doesn't do
anything (hence "dummy" package).  I think a better route is to use
Provides.  I think the dummy package approach is better reserved for
cases of major package splits.

> 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.
> 
OK.  So let's get to it :-)

Regards,

-Roberto

-- 
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com
-------------- 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/20061017/68b35151/attachment.pgp