[Pkg-Cyrus-imapd-Debian-devel] Re: [Pkg-cyrus-sasl2-debian-devel] Kicking off

Sven Mueller sven at incase.de
Tue Dec 13 15:53:45 UTC 2005


Fabian Fagerholm wrote on 12/12/2005 22:48:

[I'm cross-posting this to the cyrus-imapd packaging ML, since it
concerns cyrus-imapd packaging, too]

I will just comment on the items I can say anything about:

>       * Which libdb should we link with? My suggestion is to keep with
>         whatever is used with the cyrus-imapd packages.

Well, the question is valid (as HMH already pointed out) and whatever we
choose, it should certainly be (made) the same as with the cyrus-imapd
packages. Which could mean that we have to change the DB we are linking
against on the cyrus-imapd side of the fence.

>       * Which MySQL library should we link with?

Well, libmysqlclient12 (MySQL 4.0) is too old IMHO, so we can only
choose between libmysqlclient14 (4.1) and libmysqlclient15 (5.0). IMHO,
we should allow for both but default to libmysqlclient14. After all,
SASL doesn't use any features specific to MySQL 5 and the older clients
 us the newer database (they just won't be able to use the new features).

>       * Update libtool and auto* stuff -- at build-time?

I would say: Yes.

> Wishlist for the packaging / Workflow
> -------------------------------------
> 
>       * Follow the same workflow as the Cyrus IMAPd packages:
>               * Use the same SVN repository layout.

If we want to use the svn-buildpackage merge-with-upstream feature, we
will need a different layout. However, it would probably save us some
work in the long run if we learn to do it.

[documentation needed]
>       * A summary of how the SVN repository is laid out: the commands
>         used to create the current repository with the
>         merge-with-upstream feature of svn-buildpackage.

I would certainly appreciate a summary of how the repository needs to be
laid out to use that feature and how we can use dpatch-edit-patch (or an
equivalent script) to create/modify/update our dpatch files.
If I had such a summary anywhere, I could rework the cyrus-imapd
repository to match the same layout (using svn-dumpfilter and thus
preserving file modification history).

>       * A summary of how the dpatch stuff has been integrated, or just a
>         note saying that it's completely standard and thus documented in
>         dpatch docs.

As far as cyrus-imapd goes: It is completely standard and documented in
the dpatch docs. Possibly with one exception of
98-use_Debian_config.guess_config.sub.dpatch which is not a patch
really, but a script modifying the source tree (but even that approach
to "patching" is described in the dpatch docs).

cu,
sven



More information about the Pkg-Cyrus-imapd-Debian-devel mailing list