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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=Febzp
	x2FDu6NH3zIjGNuGFQrEMWtjZDJwjfQSqbV67Omj5r2SNS3L/jxApr4Bcrx/c3yv
	Bwj1rOWAjnyOkvTY2+Go/+dhiL0gLxU9TUGbleh338xi7pErXdFZGq01TuNlD1jw
	Ti02zvtfxHUjM5wW5BnSuzJ2IlB5n5nCyg6TCI=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=Y8QdwGf2ZD3
	na3ugA2tFRd0T5ok=; b=dJNvXyY3lH5VoX696Fn/xNXc5Abj8gX6rJTZqGNCINn
	zsPQFhPT2GWgRmmAHHYtKbFt68N/MbGPc5NeThgeNl6rxQ67YPlM8fIWHc77AKFd
	sL+QYSYG+08i/tlLIce43jGm/27J6TshLRXuI++PWqWtIciiogEhK2tF60pSGWg8
	=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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-Spam-SWARE-Status:	No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=postinstall, gate, Singles, H*MI:invalid
X-HELO:	vsmx009.vodafonemail.xion.oxcs.net
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: base-files revisited
References:	<CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ AT mail DOT gmail DOT com>
Date:	Mon, 08 Apr 2019 18:56:33 +0200
In-Reply-To:	<CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ@mail.gmail.com> (John Morrison's message of "Sat, 6 Apr 2019 15:08:12 +0100")
Message-ID:	<87r2aczb9a.fsf@Rainer.invalid>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version:	1.0

John Morrison writes:
> I've been asked at work to get the standard base-files extended with
> specifics for the company I work for and wondered if this would be a good
> time to revisit how the .bashrc file in particular is put together.
>
> What I was considering would be introducing a ~/.bashrc.d/ folder and
> splitting the existing ~/.bashrc file into its component parts;
>
> * alias.bashrc
> * completion.bashrc
> * functions.bashrc
> * history.bashrc
> * shell.bashrc
> * umask.bashrc
>
> and changing .bashrc to source all the *.bashrc files.
>
> This would allow easier extension of the bashrc with, in my case, company
> specific options (proxies, common aliases etc).

Been there, done that.  You'll end up providing one or more company
specific packages either as an overlay repository or merged into a local
mirror repository.  That is unless you only have a handful of users that
either can and actually do follow instructions or you can handhold them
during their installations.  If you provide a company config package all
you need to do is make sure it gets installed last (or arrange for the
postinstall to do all the work and move that to a late place).  Once
you've replaced the default files setup (or rather the respective
postinstalls) will keep them untouched.

> I was also thinking of taking some more of the sample from
> https://www.tldp.org/LDP/abs/html/sample-bashrc.html, for example the
> colours and some more of the aliases and adding them into the existing sets.

None of that strikes me as desirable to enable by default.

> Thoughts?
>
> I think Achim Gratz took over the base-files from me. Achim, are you still
> around? Open for a discussion?

Tentatively, I'd say what you want to do doesn't belong into base-files.
That is supposed to provide a clean starting point (mostly to work
around some quirks of how Windows leaves your environment) and treat all
POSIX shells the same to the extent possible, not create even more
differences than there are out of the gate.  There already are hooks in
profile to enable your own scripting if that's what you want and
anything that is purely bash-specific would need to go into its own
package anyway.


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

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

- Raw text -