On 2 August 2015 at 22:57, Jonathan Underwood
<jonathan.underwood(a)gmail.com> wrote:
On 2 August 2015 at 15:29, Marcin Haba <marcin.haba(a)bacula.pl>
wrote:
> My image of configuration files is that they are files for read/write
> purpose by design, because they enables _configure_ something
> (application, service, single program, script...whatever). If they are
> dedicated only for reading then from my point of view they lose
> "configuration" meaning (something like WORM storage ;-) ).
>
This is probably an argument for having shell configuration fragments
packaged under /usr/lib/bash/profile.d rather than /etc/profile.d.
.. or /usr/share/bash/profile.d, perhaps.