As a system administrator and end user, the lack of a clean way to opt-in/opt-out of system-level bashrc snippets has been a decades-long frustration (eg. see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286527 which predates even this ancient bug).
As-is, if I want to opt-in or opt-out to any system-level bashrc behavior, I have to edit /etc/bash.bashrc directly, and then manually merge my changes into new /etc/bash.bashrc files any time that file is updated by the package. It would be much cleaner if there were a /etc/bashrc.d/ (or /etc/bash.bashrc.d/ or similar) path that I (as a system admin) could drop script snippets into without touching the default /etc/bash.bashrc. Most recent suggestions/patches/attempts for addressing this issue would have /etc/bash.bashrc source the existing /etc/profile.d/* (instead of creating a new /etc/bashrc.d/ or similar path). However, based on comments here and elsewhere (eg. https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2083705), it appears there is a desire to keep system-provided profile (login) and bashrc (non-login) scripts separate, and to make them primarily opt-in rather than opt-out. Based on those comments, I understand why that solution has not been implemented. However, the original suggestion in this bug (sourcing /etc/bashrc.d/* or another similar path) still has not been acknowledged/addressed. Are there any arguments against it that I have missed? If there are no objections to sourcing /etc/bashrc.d/* in the default /etc/bash.bashrc, how can we get that implemented?
