Subject: Re: [patch] Non strict dependency in rcorder
To: None <firstname.lastname@example.org>
From: David Young <email@example.com>
Date: 08/15/2006 12:34:31
On Tue, Aug 15, 2006 at 03:02:20PM +0000, Mike M. Volokhov wrote:
> Greg Troxel <firstname.lastname@example.org> wrote:
> > I don't like OPTIONAL-REQUIRE; that's too much of a semantic clash.
> > How about
> > BEFORE-IF-PRESENT:
> > AFTER-IF-PRESENT:
> > This avoids using REQUIRE (since these aren't actual requirements,
> > just ordering constraints), and expresses the "if foo is here, this
> > has to go before foo, but if not don't worry" quite naturally (to me
> > anyway).
> Hm, sounds reasonable. How about adding AFTER as alias to REQUIRE then?
AFTER doesn't mean the same thing. Also, adding aliases will make
the rc.d scripts harder to interpret and to search, and it may break
David Young OJC Technologies
email@example.com Urbana, IL * (217) 278-3933