This is the mail archive of the
mailing list for the Cygwin project.
Re: [PATCH] Postinstall script ordering in setup - take 2
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: "Pierre A. Humblet" <Pierre dot Humblet at ieee dot org>
- Cc: Max Bowsher <maxb at ukf dot net>, <cygwin-apps at cygwin dot com>
- Date: Tue, 4 Mar 2003 15:56:17 -0500 (EST)
- Subject: Re: [PATCH] Postinstall script ordering in setup - take 2
- Reply-to: cygwin-apps at cygwin dot com
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 passwd-grp.sh 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.
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 passwd-grp.sh 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...
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!