On Fri, Feb 02, 2007 at 04:08:30AM +0100, Roland Mainz wrote:

> Umpf... it can quickly happen if the maintainer is not available for a
> week and someone else wants a "quick" update. Mozilla.org, Gnome.org,
> X.org etc. are good examples - maintainer on vacation for some weeks and
> others start messing his code up (there is a german sentence describing
> this kind of situation: "Ist die Katze aus dem Haus tanzen die M?use auf
> dem Tisch" ... rougthly translated: "The cat is away from home and the
> mice start dancing on the table").

I think we can handle the cat going on vacation for a few weeks.  But if
the cat leaves for better pastures (not enough mice? :), then the cat has
little right to complain about the dancing mice.

> Offtopic: Who maintains this code in Solaris ?

I'd ask Casper about this, I think, though it's pretty much unmaintained --
almost everything in cmd/tcpd hasn't been touched since integration in
2001.

> > The grub patches are baked into the sources already; I can't comment on why
> > they continue to exist as separate entities.  Perhaps Jan can.
> 
> If the GRUB people where allowed to add such files as part of their work
> why can't we do the same ?

If I'd been more careful about the newboot review, I probably would have
asked for these files not to have been integrated.

> > Indeed, the ON build log shows no instances of the patch utility being run
> > to apply diffs to the source.
> 
> Erm... that was NOT the idea. I did not intend to run "gpatch" or
> "patch" at build time.

Ah.  That's a great relief, though I still feel like these files (or
equivalents) belong in a development workspace, and not in ON.

Danek

Reply via email to