X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type; q=dns; s=default; b=uhQ6 8Bzb1OO0FXGUqLXIDFHPYjYJH92uzT6ZnZUpadlveLKFJjRrPP7Fdx/4bCMpZ5uM 8WAJHAB4tLDzvISqSKXv7amNKs8zu20I3bLLd2VWRXd50kB9pHH9VSPB5Q5nWWVF 0ct8K560qD9X3hC5CLxce3QI82fAK/qNuXZiH10= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type; s=default; bh=rgWSzELNYL b+QzHytY1sOjtTBhY=; b=fBluhEl2GH2ss3ZW/JCvo7SGsu1lZBuOLrfz60nQ+K 38Lt/hhtlvHfm+F3KnWnCFQNmwPHtAmmuzG4xjPNnZ5IGtFGsj3QqVMMpKo/q/Km X6rN4A5G6kakbQMEh946fYSTKUv2G+F9vAJKistVYjYvC1t21X7eeSqo18ovo/B/ g= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*f:sk:87a8lci, H*i:sk:87a8lci, H*MI:sk:87a8lci, Repin X-HELO: mx1.redhat.com Subject: Re: How to install a custom permanent postinstall handler? To: cygwin AT cygwin DOT com References: <838469265 DOT 20160401235308 AT yandex DOT ru> <87a8lcicxg DOT fsf AT Rainer DOT invalid> From: Eric Blake Openpgp: url=http://people.redhat.com/eblake/eblake.gpg Message-ID: <56FFD48C.4000802@redhat.com> Date: Sat, 2 Apr 2016 08:17:48 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <87a8lcicxg.fsf@Rainer.invalid> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VnaiF3WLw95KNG0amGAD9k8ChEl7i2Cx6" X-IsSubscribed: yes --VnaiF3WLw95KNG0amGAD9k8ChEl7i2Cx6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/02/2016 03:21 AM, Achim Gratz wrote: > 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 =3D /bin/dash . >> But every time bash update, it overwrite the link. >=20 > I think the correct course of action would be to put /bin/sh under > control of the alternatives system. Since I maintain both dash and bash, I'm game for setting up /bin/sh as an alternative. However, I've never targeted the alternatives system before as a package maintainer; any advice on docs or an example that I could copy from? I would probably make the defaults give bash higher priority over dash, but with the alternatives in place, it would be easy for a local user to swap the priorities on their system; I'd probably also want to provide a convenience script to make swapping default sh an easier task than users having to actually call directly into the alternatives system. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --VnaiF3WLw95KNG0amGAD9k8ChEl7i2Cx6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW/9SNAAoJEKeha0olJ0NqVZgH/ivsPHKiPNVGlr1sAYcBTL3P cjIdjD55ZobU6YHzuLd/XDwDpkWPQaqRwEEYOTaP/TtNuXDxpYNhZzHSR5a3lvzW /k01sa1NqxkDttGCDXV/Pe+HU/OoOhGjuFVby0HhdLN0s5ADapIp+yFaZT6IvyQv O8C4TpB0RCWxo4x4sbHOd1PmoRy8PcAixNj3F/rJ25Z0dXqllU1mTnetWqMOVqiT HMggYVduQHj+PL2WNjKILMxNeKLsFd+Z7pFj0QkCIm7TF6+RpjtPxZj7iAw2U04V QOE7qDa0XgboY8fK5oR6OLwOILRf7w/AGe6pQQGc4FDqPXJrckzMvGd2LFXxZMU= =oOqP -----END PGP SIGNATURE----- --VnaiF3WLw95KNG0amGAD9k8ChEl7i2Cx6--