patchThe GNU Bourne-Again SHell - Patches: patch #9934, support for .bashrc.d config...


You are not allowed to post comments on this tracker with your current authentication level.

patch #9934: support for .bashrc.d config directory

Submitter:  Piotr Henryk Dabrowski <dabrowski>
Submitted:  Thu 14 May 2020 11:55:49 AM UTC
Category:  None Priority:  5 - Normal
Status:  Wont Do Privacy:  Public
Assigned to:  None Open/Closed:  Open

Mon 18 May 2020 02:13:50 PM UTC, comment #3: 

I understand that perspective.

There is a different one: that a good idea will eventually gain enough support to be widely available.

This isn't something that needs to be embedded in C code. It's so trivial to do outside the shell itself, that should be where the effort is focused.

I would concentrate on getting a vendor or distribution to support this construct and go from there.

Chet Ramey <chet>
Group administrator
Sat 16 May 2020 10:57:19 AM UTC, comment #2: 

@Chet Ramey

Unfortunately entrusting this task to a separate script defies the whole idea.

For people to start using ~/.bashrc.d for their pieces of scripts it must be
guaranteed that support for it is widespread and standardized.

If it doesn't come out-of-the-box with Bash, then every distribution would have
to provide that script somewhere (/etc/profile? /etc/profile.d? /skel/.bashrc?).
Which will take forever to actually happen.
And still nobody will trust this. Not wanting to risk that their piece of code
they put into ~/.bashrc.d won't work, they will continue to flood ~/.bashrc
knowing this will work everywhere.
This way nothing is going to change.

Piotr Henryk Dabrowski <dabrowski>
Thu 14 May 2020 12:34:23 PM UTC, comment #1: 

This is not a bad idea, but it should not be in the shell itself.

It's too easy to do as a script; there's no reason to embed it in C code.

Chet Ramey <chet>
Group administrator
Thu 14 May 2020 11:55:49 AM UTC, original submission:  

Execute config files from ~/.bashrc.d/ (and optionally /etc/bash.bashrc.d/) directories.

There are lots of 3rd party software (especially installers) or poorly designed solutions doing this:
  echo ... >> ~/.bashrc
and creating unmaintainable mess in user's .bashrc file.

With this patch separate config files in ~/.bashrc.d/ can be used. Which allows for separation of content from different origins (including /etc/skel) and makes it easy to clean up the config.

Piotr Henryk Dabrowski <dabrowski>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attached Files
file #49065:  0001-support-for-bashrcd-config-directory.patch added by dabrowski (3KiB - text/x-patch - 0001-support-for-bashrcd-config-directory.patch)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by chet (Posted a comment)
  • -email is unavailable- added by dabrowski (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-05-14 chet StatusNone Wont Do
    2020-05-14 dabrowski Attached File- Added 0001-support-for-bashrcd-config-directory.patch, #49065

    Back to the top

    Powered by Savane 3.13-b921.
    Corresponding source code