Bug 1959284 - bash should read startup files from ~/.config/bash/{profile,bashrc}, if available
Summary: bash should read startup files from ~/.config/bash/{profile,bashrc}, if avail...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bash
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Siteshwar Vashisht
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-11 08:07 UTC by Allison Karlitskaya
Modified: 2022-01-17 21:06 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-01-17 21:06:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Allison Karlitskaya 2021-05-11 08:07:56 UTC
bash remains, doggedly, one of the few things on my system that isn't following the xdg basedir spec for storage of its configuration files, and it's the one thing that's almost impossible to fix, due to lack of relevant environment variables, and the fact that it's run on login, with no control over its parameters.

It would be lovely if bash would read these files:

 - ~/.config/bash/profile
 - ~/.config/bash/bashrc

if they are present, as alternatives to ~/.bash_profile and ~/.bashrc.

Comment 1 Allison Karlitskaya 2021-05-11 08:08:48 UTC
I've sent a patch upstream here: https://lists.gnu.org/archive/html/bug-bash/2021-05/msg00024.html

Comment 2 Allison Karlitskaya 2021-05-11 08:27:16 UTC
...and a PR here: https://src.fedoraproject.org/rpms/bash/pull-request/27

Comment 3 Siteshwar Vashisht 2021-11-01 11:16:29 UTC
I still don't see this patch merged upstream[1] nor there is any update on mailing list.

Allison,

Would it be fine if this issue is directly discussed upstream ? I would pick up the patch during a rebase (rather than adding it separately in Fedora) if it gets merged.

[1] https://git.savannah.gnu.org/cgit/bash.git/log/?h=devel

Comment 4 Allison Karlitskaya 2021-11-02 10:21:10 UTC
The latest update from upstream isn't very promising looking:

  https://lists.gnu.org/archive/html/bug-bash/2021-05/msg00093.html

and unfortunately there's no actual bug tracker.

I don't imagine that this "not a high priority issue" from half a year ago will be spontaneously revisited by the maintainer at this point.

If I had to guess, I'd say this idea is basically dead due to maintainer disinterest. :(


Could we possibly address this on the Fedora side with hooks in our shipped bashrc/profile?

Comment 5 Siteshwar Vashisht 2021-11-02 10:39:02 UTC
(In reply to Allison Karlitskaya from comment #4)
> The latest update from upstream isn't very promising looking:
> 
>   https://lists.gnu.org/archive/html/bug-bash/2021-05/msg00093.html
> 
> and unfortunately there's no actual bug tracker.
> 
> I don't imagine that this "not a high priority issue" from half a year ago
> will be spontaneously revisited by the maintainer at this point.
> 
> If I had to guess, I'd say this idea is basically dead due to maintainer
> disinterest. :(
> 
> 
> Could we possibly address this on the Fedora side with hooks in our shipped
> bashrc/profile?

I don't try to deviate from upstream. However, I will nudge Chet again about your patch.

Comment 6 Siteshwar Vashisht 2022-01-17 21:06:40 UTC
Closing due to lack of progress after Chet's response[1].

[1] https://lists.gnu.org/archive/html/bug-bash/2021-11/msg00045.html


Note You need to log in before you can comment on or make changes to this bug.