From: John Morrison <john@morrison.ec>
To: Brian.Inglis@systematicsw.ab.ca, cygwin@cygwin.com
Subject: Re: base-files revisited
Date: Mon, 08 Apr 2019 17:46:00 -0000 [thread overview]
Message-ID: <CAAgpg9ZTKzfbOrtLJ__M-uZ4_JmvkqQRePb0BYCPJCbRc5GyMw@mail.gmail.com> (raw)
In-Reply-To: <147454c3-692f-a541-4019-a557773faff7@SystematicSw.ab.ca>
On Mon, 8 Apr 2019 at 08:05, Brian Inglis wrote:
> 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.
>
> 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.
>
I'm sure these would work or could be made to, but this is intended to be a
starting point for users to modify (with company placeholders), not
globally enforced, but thanks!
I've got a base-files-<company> package, but wanted to extend the .rc files
installed by base-files. Achim has proffered some ideas along that front
(see other mail).
I wasn't trying for something unique, just trying to get things a little
easier to customise :)
--
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:[~2019-04-08 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 14:08 John Morrison
2019-04-07 18:58 ` Chris Wagner
2019-04-08 7:05 ` Brian Inglis
2019-04-08 17:46 ` John Morrison [this message]
2019-04-08 16:56 ` Achim Gratz
2019-04-08 17:37 ` John Morrison
2019-04-08 18:25 ` Achim Gratz
2019-04-08 19:04 ` Brian Inglis
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=CAAgpg9ZTKzfbOrtLJ__M-uZ4_JmvkqQRePb0BYCPJCbRc5GyMw@mail.gmail.com \
--to=john@morrison.ec \
--cc=Brian.Inglis@systematicsw.ab.ca \
--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).