This is the mail archive of the
mailing list for the Cygwin project.
Re: How to install a custom permanent postinstall handler?
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Sun, 03 Apr 2016 08:24:02 +0200
- Subject: Re: How to install a custom permanent postinstall handler?
- Authentication-results: sourceware.org; auth=none
- References: <838469265 dot 20160401235308 at yandex dot ru> <87a8lcicxg dot fsf at Rainer dot invalid> <5700975A dot 3070002 at cygwin dot com>
Yaakov Selkowitz writes:
> I am not in favour of /bin/sh being alternatives-able.
I'd posit that it should not be bash then and somwone else might
reasonably want a different /bin/sh, perhaps even bash. Which is
exactly why the alternatives system exists.
> The *proper* course of action is to use the shebang for the script
> interpreter you require, i.e. /bin/dash.
It's perfectly OK to use /bin/sh (I'd even recommend it) if all you want
is a POSIX shell. You shouldn't be trying to use local then, but that's
another story (*).
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple