From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: How to install a custom permanent postinstall handler?
Date: Sat, 02 Apr 2016 09:21:00 -0000 [thread overview]
Message-ID: <87a8lcicxg.fsf@Rainer.invalid> (raw)
In-Reply-To: <838469265.20160401235308@yandex.ru> (Andrey Repin's message of "Fri, 1 Apr 2016 23:53:08 +0300")
Andrey Repin writes:
> Couple of my scripts rely on ASH/DASH functionality that is not present in
> BASH. (Namely "local -".)
> To amend that, I make a symlink /bin/sh = /bin/dash .
> But every time bash update, it overwrite the link.
I think the correct course of action would be to put /bin/sh under
control of the alternatives system.
> So… How would I go about creating a handler that would restore the parity?
> Will making a script /etc/postinstall be enough, or some additional magic is
> necessary?
There is. You will want to run this script in postinstall stratum z as
a perpetual one, so the name of the script needs to start with "zp_"
(preferrably with a .dash suffix, too).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-04-02 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 21:05 Andrey Repin
2016-04-02 9:21 ` Achim Gratz [this message]
2016-04-02 14:18 ` Eric Blake
2016-04-02 14:56 ` Achim Gratz
2016-04-03 4:09 ` Yaakov Selkowitz
2016-04-03 6:24 ` Achim Gratz
2016-04-03 11:47 ` Dirk Fassbender
2016-04-03 12:02 ` Achim Gratz
2016-04-03 18:06 ` Yaakov Selkowitz
2016-04-03 23:20 ` Andrey Repin
2016-04-04 6:09 ` Yaakov Selkowitz
2016-04-04 11:20 ` Andrey Repin
2016-04-04 14:42 ` Eric Blake
2016-04-04 15:37 ` Helmut Karlowski
2016-04-04 15:53 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8lcicxg.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).