[Pkg-Cyrus-imapd-Debian-devel] Upload to debian/experimental?

[Henrique de Moraes Holschuh]

On Thu, 28 Apr 2005, Sven Mueller wrote:
> Since the package is now pretty well tested, at least as far as I'm
> concerned, I would like to reach a wider audience and get the package(s)
> into experimental.

Go ahead!

> Are there any reasons against this?

I don't think so.  Please don't upload it to unstable yet, but an upload to
experimental is fine.

> to the libcyrus-imap-perl22 package. Actually, I've already done so and
> websieve still works perfectly fine. I also checked the API of both perl
> bindings, and the cyrus22 version seems 100% backward compatible.

If the API is 100% compatible (and I believe perl has no such a thing as an
ABI problem in this matter. Is that correct?) then yes, we might as well
provide the old API with a provides: header.

> We could also supply dummy packages for the cyrus21 series which pull a
> cyrus21 installation up into a cyrus22 installation. I did so on my test

No.  Cyrus21 will remain in sarge and sid for a while...

> PS: For my taste, the cyrus22 packages already seem stable enough to
> even go into sarge, but since Henrique already expressed that he doesn't
> want them to go into sarge, I guess I can't get my wish here ;-)

Please, let's leave it out of official sarge, there are some... issues
upstream that, when fixed, will cause us to *really* want to get everyone to
use such packages.  So, I'd rather we fully support sarge users thorugh an
outside apt repository and mailinglist in alioth...

Examples of such issues: murder mupdate troubles, 8192-char linewrapping
bug, some suspicious segfaults here and there.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh