This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Postinstall script ordering in setup - take 2

Igor Pechtchanski wrote:
> On Tue, 4 Mar 2003, Pierre A. Humblet wrote:
>> At 06:52 PM 3/4/2003 -0000, Max Bowsher wrote:
>>> Do we also need a way to mark 'high-priority' scripts?
>>> i.e. ones that should run before all others.
>>> I'm thinking about mainly.
>> Good point. Any other script doing a chown would need it, but that's
>> all I can think of (so far).
>> Starting with 1.3.21 the "if [ -x/r/w ... ]" test won't depend on it.
>> Pierre
> If that's all it is, then there is no need for special treatment.
> It's a simple rule: if your script does a chown, include
> in its dependences, that's all.
> I thought it was more like "something is essential to running all
> scripts, so there had better be a dependence there whether the author
> included it or not".  Can't think of any that would need it, though...

Neither can I, specifically. We will see if John has a specific requirement
for his run-last idea.

What I was thinking of, is that a script could be tagged high (or low)
priority, and setup would simply determine which scripts to run, then sort
the list by priority.

Whilst I'm thinking about it, how does your patch handle circular


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]