This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: HEADSUP maintainers: Packages install scripts without execute ?permissions
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com, cygwin-apps at cygwin dot com
- Date: Mon, 22 Jun 2009 17:01:05 +0200
- Subject: Re: HEADSUP maintainers: Packages install scripts without execute ?permissions
- References: <4A3D1570.5020506@aim.com> <20090622094310.GN5039@calimero.vinschen.de> <20090622131144.GR5039@calimero.vinschen.de> <4A3F8955.3080407@gmail.com> <20090622134020.GS5039@calimero.vinschen.de> <loom.20090622T135114-330@post.gmane.org> <20090622140922.GU5039@calimero.vinschen.de>
- Reply-to: cygwin-apps at cygwin dot com
On Jun 22 16:09, Corinna Vinschen wrote:
> On Jun 22 13:58, Eric Blake wrote:
> > For that matter, are there any postinstall scripts currently relying on a
> > different interpreter? If not, then I'm in favor of the idea of changing
> > setup.exe to be immune to the execute bit on postinstall scripts, at the
> > expense of making postinstall scripts locked into bash (at least, as the
> > initial interpreter).
>
> There can be only *.bat and *.sh files in /etc/postinstall and
> /etc/preremove. *.bat files are started via `cmd /c file' and *.sh
> files are started via `bash --norc --noprofile -c file'. So we sort of
> require a script to be a sh/bash script anyway right now. Admittedly, I
> did not actually *look* into all postinstall/preremove scripts in the
> distro.
I just checked the entire 1.7 distro and here's the result:
We have not a single package left which uses a .bat file in postinstall
or in preremove. That's great, IMHO.
And, AFAICS, all of the *.sh fiels are actually some variation of
sh/ash/bash script.
So I assume it's safe to remove the -c from setup's script starter
method.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat