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

[Henrique de Moraes Holschuh]

On Mon, 02 May 2005, Sven Mueller wrote:
> not HEAD), cyrmaster doesn't listen for nntp connections even though
> they are set up in cyrus.conf.

Then let's leave cyrus.conf well enough alone...

> While I somehow agree with you, almost all HowTos I found recently were
> talking about /etc/cyrus/cyrus.conf and /etc/cyrus/imapd.conf. And that
> also seems to be where most distributions seem to put the files today.

Which ones?  I have never seen any.  We *can* move those conffiles to
/etc/cyrus, but that requires the usual dpkg conffile-moving pains.

> Oh well, I have no strong opinion there.

Nor do I.  But I wouldn't touch conffile moves unless they are well worth
the effort.

> I currently think about removing the autotools-dev build dependency.

Don't.

> Most packaging infos recommend not to pull config.sub and config.guess
> in at build time. Any good reason to keep pulling them in instead of
> pulling them in manually when preparing the package? I guess there are,
> otherwise you wouldn't have created the autotools-dev package.

Those misguided paranoids think they actually get some measure of control
from non-automatic config.sub updates (config.guess is not even USED by any
proper debian package, certainly not by any of mine :-) )... which proves
they know nothing about the idea behind autoconf and automake, or the
philosophy behind them, either :)

If you build-depend on autotools-dev, a new port can fix all issues it might
have by updating by force autotools-dev before they compile the archive. So,
that's the correct way of using it for Debian packages.

> Mostly because I don't trust it regarding regeneration of some files,

Heh, the debian/deletable.files hack needs some work, and it *requires* the
.orig.tar.gz tarball in the parent directory of the build tree for proper
updating :)   Most of the time, it should be empty, only at final build
should it look at the svn/cvs export, compare to what is in the tarball, and
promptly rm the difference.

If it is causing trouble with your svn setup, just comment the part of
autogen.sh that writes a non-empty deletable.files.  It is better to keep
the code in debian/rules that deals with autotools-dev and autogen.sh
active.

> especially debian/deletable.files (or whatever it is actually called).
> It creates an empty file there. Any hint from the author? ;-)

I have yet to try to use svn-buildpackage.  I will soon, and when that
happens, expect a lot of patches to make it work as neatly as it did with
cvs-buildpackage.  Then you will see why I like those hacks :)

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