DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=iEGnk
	MvYJopMLQ6icxb8PddmdgTwFEtcWtCXIy04p5ZUnwcUlnkxp5ZmhE8szoGMmrXGZ
	119i2VX0+zkWIjDSrVa9p9qLlg3v/3OJ3VC1OTJ7bvAHaQbMCUlgPvseb9DBFlcE
	gnXEwoRAvBy4gKAnDrQP6486emvYwFZlXI6mlQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [Attn: base-files maintainer] Changing /etc/profile to add more shell-dependent settings
References: <20151014155256.GN14466@dinwoodie.org>	<876129s86w.fsf@Rainer.invalid> <20151014171400.GP14466@dinwoodie.org>
Date: Wed, 14 Oct 2015 22:15:51 +0200
In-Reply-To: <20151014171400.GP14466@dinwoodie.org> (Adam Dinwoodie's message	of "Wed, 14 Oct 2015 18:14:00 +0100")
Message-ID: <87h9ltqk94.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Adam Dinwoodie writes:
> The only other option I can think of is to rename the .bash file to .sh
> and to patch it to check $BASH_VERSION before running the Bash-specific
> code.  That seems fragile though -- it means putting Bashisms in a
> script that may be run by non-Bash shells (even if it's gated by
> checking $BASH_VERSION), and it means a patch of the upstream fzf Bash
> script in a way that's essentially just duplicating code already in
> /etc/profile.

Sourcing that script would actually belong into /etc/bash.bashrc if I
understand correctly what this is supposed to do.  Unfortunaltely there
is no infrastructure set up to do this yet in bash.bashrc and simply
changing the file makes it non-upgradeable.  OTOH what I see there on my
Linux system is far too complicated for Cygwin, I'll have to think about
this some more.

> (The upstream solution to this is to add code to the user's ~/.bashrc to
> source the relevant scripts, but I don't think that's feasible when
> installing the scripts via setup-*.exe.)

No, that should indeed be left to the user.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
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