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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=qErWMfy/LSAn0+Hy
	d+i0Po1744fDXY/TgBrDtY1Y0OBZpYDor6rHXBfP1Ph3us8CWgwGkYHYaQoZVoHi
	unAqLVlfgVEz4LS6gn8fMGeUp/6tmuW2YM395AFV8LWwQfRARzuH4AG4zCSmunoY
	D7DwDqoMq/KhWRtwpbO/dOdodbc=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=kktynbOEtYSmjNCsbLCMul
	CQ95k=; b=C+D3M+2b9IEt5E5vSvf+QmQAwyVaGhk3TrSB4sMXNZOF46EsitrSsc
	1dDUjzNNRoYsCEBbUYqWhqW9xuxtOVD1+vsyUxKAwVPGyIRzeNJwt44PD+kcRW1U
	32+vCiXUx10tissjJf/sBSGxRkgHrE/PS4l0Q4ZDIwAFnrieExIec=
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.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,TBC autolearn=no version=3.3.1 spammy=customization, H*R:D*ca, company, driver
X-HELO: smtp-out-so.shaw.ca
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: base-files revisited
To: cygwin AT cygwin DOT com
References: <CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ AT mail DOT gmail DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <147454c3-692f-a541-4019-a557773faff7@SystematicSw.ab.ca>
Date: Mon, 8 Apr 2019 01:05:43 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-04-06 08:08, John Morrison wrote:
> 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).
> 
> 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.
> 
> Thoughts?
> 
> I think Achim Gratz took over the base-files from me. Achim, are you still
> around? Open for a discussion?
> 
> Kind regards

You might want to consider using standard /etc/profile.d/ scripts named for, and
conditional on, your company domain, Cygwin, shell, and components, depending on
how you want to do things, possibly installed from /etc/defaults/etc/profile.d/.

Or you could put a <domain>.sh driver script in /etc/profile.d/, and source
scripts from /usr/local/{bin,lib,share}/<domain>/.

You could use the Xwin directories ~/.local/ and ~/.config/ if you want user
specific customization, perhaps setup in /etc/defaults/etc/skel and installed by
a custom postinstall script base-files-<domain>.sh.

Or some combo of those and other standard approaches to local customization,
like .${OSTYPE}_profile, .${OSTYPE}rc, .${HOSTNAME}_profile, .${HOSTNAME}rc, etc.

Have a look at the various systems and shells and their initialization and
customization approaches, and adapt some existing infrastructure, rather than
stuffing something unique somewhere unexpected.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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