Why new package name libsasl2-2

[Roberto C. Sanchez]

On Mon, Oct 16, 2006 at 08:30:03AM +0300, Fabian Fagerholm wrote:
> 
> *sigh*
> 
> Are you guys paying attention? :)
> 
Yes.  I am paying very close attention now.  :-)

At this very moment I am in the midst of renaming everything back
(again).

> Read policy, the library packaging guide and the posts sent to this list
> when I started this thing.
> 
Yes.  I had missed the early posts since I only went from the August
status report.

> 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.
> 
Good to know.

> I first considered just updating the old (cyrus-sasl2) package with the
> new upstream version. However, I quickly realised that the packaging
> would end up totally replaced, and I would waste time doing the same
> work twice. So I started over, and got to the same point packaging-wise
> as the old package in a matter of weeks.
> 
OK.  How do you feel about the inclusion of the old changelog entries
from the former package?

> Also, I think it's very late to start working on getting this package
> into etch. It's a critical and difficult package, and those who wanted
> it in should have started investing time at the beginning of this year.
> If I had a package that depended on cyrus-sasl2, I would be very
> reluctant to accept a change at this time. I anticipated this from the
> start (based on the involvement in this project at the time) and wanted
> to make sure we don't interfere with other packages while bringing this
> into experimental and then sid.
> 
I agree that it is late.  However, I think if it is at all possible, we
should try and get it into Etch.  Anothe entire release cycle with the
old cyrus-sasl2 does not please me.  I think that we can do it.

> 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.

OK.  Got it.  Nearly ready to commit the names back to how they were.

Regard,

-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/20061016/d0e46991/attachment.pgp