From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: 29337-done@debbugs.gnu.org
Subject: bug#29337: Bash reads system-wide bashrc unconditionally.
Date: Mon, 11 Dec 2017 14:19:46 +0100 [thread overview]
Message-ID: <87zi6p1jwt.fsf@gnu.org> (raw)
In-Reply-To: <87tvwxqyzf.fsf@gnu.org> (Roel Janssen's message of "Mon, 11 Dec 2017 12:35:22 +0100")
Roel Janssen <roel@gnu.org> skribis:
> Ludovic Courtès writes:
[...]
>>>> Now, we’re compiling Bash with "-DSYS_BASHRC='\"/etc/bashrc\"'". I
>>>> wonder if removing that flag solves the --init-file case.
>>>
>>> It does. So, I have a custom bash package for my specific use-case.
>>> I'm not sure how it affects other functionality, but I would like it if
>>> we could make this change upstream at some point.
>>
>> Now’s the time to make that change in ‘core-updates’!
>>
>> I don’t think it breaks things on GuixSD because /etc/profile sources
>> /etc/bashrc anyway.
>>
>> Thoughts?
>
> I don't think it'll break things. So I guess I'm too late for the
> core-updates cycle.
Yes.
> Should I push this change to core-updates for the next cycle?
You can create a ‘core-updates-next’ branch based on ‘core-updates’, or
wait until ‘core-updates’ has been merged (which could take at least two
weeks.)
Ludo’.
next prev parent reply other threads:[~2017-12-11 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 12:16 bug#29337: Bash reads system-wide bashrc unconditionally Roel Janssen
2017-11-17 21:04 ` Ludovic Courtès
2017-11-20 21:48 ` Roel Janssen
2017-11-21 8:50 ` Ludovic Courtès
2017-11-24 15:46 ` Roel Janssen
2017-11-24 20:51 ` Ludovic Courtès
2017-12-11 11:35 ` Roel Janssen
2017-12-11 13:19 ` Ludovic Courtès [this message]
2017-12-11 15:31 ` Roel Janssen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zi6p1jwt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29337-done@debbugs.gnu.org \
--cc=roel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).