Bug 1726397

Summary: [FEATURE] Add support for ~/.bashrc.d/*
Product: [Fedora] Fedora Reporter: PHD <phd>
Component: bashAssignee: Siteshwar Vashisht <svashisht>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: admiller, jon.dufresne, kasal, kdudka, phd, svashisht
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: bash-5.0.17-3.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-04 21:44:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch for /etc/skel/.bash_profile none

Description PHD 2019-07-02 18:51:21 UTC
Created attachment 1586836 [details]
patch for /etc/skel/.bash_profile

In ~/.bash_profile add support for custom configuration files stored in ~/.bashrc.d/* directory alongside ~/.bashrc

Patch for /etc/skel/.bash_profile in the attachment:

+if [ -d ~/.bashrc.d ]; then
+	for rc in ~/.bashrc.d/*; do
+		if [ -f "$rc" ]; then
+			. "$rc"
+		fi
+	done
+fi

Comment 1 Kamil Dudka 2019-07-03 10:08:08 UTC
Comment on attachment 1586836 [details]
patch for /etc/skel/.bash_profile

I do not like the fact the settings from ~/.bashrc.d/* would override settings from ~/.bashrc .  Would it make more sense to put this code directly into ~/.bashrc ?  Then it would be fully under control of the user.  They would be able to put anything before/after all ~/.bashrc.d/* sourced scripts.

Comment 2 Ben Cotton 2019-08-13 19:07:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Jon Dufresne 2020-05-31 23:14:11 UTC
*** Bug 1842065 has been marked as a duplicate of this bug. ***

Comment 4 Ben Cotton 2020-11-03 17:12:41 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-11-24 18:45:50 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Kamil Dudka 2020-11-24 18:52:37 UTC
Still not resolved.  Reopening...

Comment 7 Siteshwar Vashisht 2020-12-04 21:45:15 UTC
https://koji.fedoraproject.org/koji/taskinfo?taskID=56790518