on 2000/06/20 09:21, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:

> Seriously, I doubt that anybody will question an optional task that is
> conditionally compiled.

+1, just make sure that it's in /optional/[taskname] or some such. I think
that a pattern was suggested in the core doc, but if not, set one that
allows for future expansion. We can fine tune as we go.

My general thought on contrib/optional tasks is that anything should be able
to go there -- a very much less controlled space. This is also one of the
reasons why I really want to keep the core simple and clean (as possible) --
because I totally want task developers to go wild and have a good base to
write on.

.duncan

Reply via email to