debian/rules questions and my plans for dual-build.

[Henrique de Moraes Holschuh]

On Fri, 05 May 2006, Benjamin Seidenberg wrote:
> 1.) In the binary-* sections, the comments are before the tabs. For some
> reason (maybe syntax highlighting), I thought they had to be after the
> tab in make files?

No idea whatsoever if this makes any difference with POSIX make, GNU make
doesn't care.

> 2.) Why doesn't configure depend on configure-stamp? Right now, it's
> useless.

Right now I don't know, but in the 2.1 packages, configure is a *real*
target, that did all the auto-fu needed to generate configure if it was
outdated or missing.

> 3.) Why does clean-patched depend on configure, both a.) because it does
> nothing and b.) at all? I can see clean-patched depending on
> patched-stamp, but not configure/configure-stamp.

During the auto-fu days, I noticed Bad Things Happened otherwise.
Basically, you do not want to need Makefile (and clean* does) before
the configure targed did its thing when doing auto-fu.

> Currently, we have --with-idle set to "poll", using poll for idle
> support. Many people perfer idled, hence the idled branch. However, for

The right thing to do is to either switch to idled, or to make it runtime
configurable.

My list of "why shouldn't we use idled" from 2.1 days was:

1. Because cyrus-master was not babysiting it (as it was not a service, but
rather a daemon which was fired-and-forgotten).

2. Because it was not widely used.

(2) is probably not true anymore, and it is high time to fix (1) if it was
not fixed already.

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