[buildd-tools-devel] Bug#566318: Bug#566318: Bug#566318: buildd: Don't ship a /etc/cron.d/buildd that's enabled by default.

[Kurt Roeckx]

On Sat, Jan 23, 2010 at 12:14:16PM +0000, Roger Leigh wrote:
> On Sat, Jan 23, 2010 at 12:17:18PM +0100, Philipp Kern wrote:
> > On Fri, Jan 22, 2010 at 10:43:16PM +0100, Kurt Roeckx wrote:
> > > Currently installing buildd is enough to try and start the daemon
> > > without even any configuration.  This is not useful.  (root gets
> > > mailed about it and things like that.)
> > 
> > I guess it's debateable if it should be in a global crontab.  However
> > it's indeed utterly useless to try to start an unconfigured buildd.
> > (Which it obviously doesn't seem to notice.)
> 
> Currently, we terminate if there are no distributions configured.
> 
>     if (!@{$self->get_conf('DISTRIBUTIONS')}) {
>         die "distribution list is empty, aborting.";
>     }
> 
> Is this what's getting mailed?

I have no idea, zobel would know, he got the mail.

> How would you prefer that we detect whether the daemon has been
> configured?

Maybe the presense of a .builddrc file?


Kurt