The largest problem I see with this is that the things in /etc/rc.d will
get run before /usr/{local,pkg}/etc/rc.d, which is where most of the
third-party stuff is destined, and that of course won't be taken
into account by the initial run of rcorder -- it has to happen in
/etc/rc.d/local (which seems to me to have its own very special
problems,
as ${LOCALBASE}/etc/rc.d cannot depend on anything in /etc/rc.d
due to not being able to resolve those dependencies).

--*greywolf;


-----Original Message-----
From: current-users-owner@NetBSD.org
[mailto:current-users-owner@NetBSD.org] On Behalf Of Jason Thorpe
Sent: Wednesday 04 February 2004 08:41
To: Mike M. Volokhov
Cc: current-users@NetBSD.org; tech-userlevel@NetBSD.org
Subject: Re: Non strict REQUIRE/BEFORE in rcorder(8)


On Feb 4, 2004, at 8:18 AM, Mike M. Volokhov wrote:

> When we create some rcorder compliant script, it is always covenient
to
> specify some dependencies on few other scripts. This is available via
> REQUIRE/BEFORE keywords.
>
> But if that keywords will contains non-existent providers, this will
be
> treated as error. At the other hand, there are may be some cases when
> that way is not an errorous one and in addition is very covenient.

Yah, I've been wanting a feature like that, as well.

Perhaps it's better written as new keywords:

MAYBE-REQUIRE
MAYBE-BEFORE

I think that makes it a little more obvious than a ? at the end of the 
word.

         -- Jason R. Thorpe <thorpej@wasabisystems.com>