unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: 30379@debbugs.gnu.org
Subject: [bug#30379] [PATCH] gnu: bash: Don't specify default configuration filenames.
Date: Fri, 09 Feb 2018 15:06:47 +0100	[thread overview]
Message-ID: <87zi4iz288.fsf@gnu.org> (raw)
In-Reply-To: <87a7wlkp3a.fsf@gnu.org> (Roel Janssen's message of "Wed, 07 Feb 2018 12:39:09 +0100")

Hi,

Roel Janssen <roel@gnu.org> skribis:

> In bug #29337 I reported a “problem” with our Bash package:  It reads
> /etc/bashrc even when it shouldn't, according to its own documentation.
> I also compared the behavior of Bash on CentOS to that of Bash on Guix
> with the following test:
>
>> On CentOS 7, the following happens (yes, I added the echo-statement to
>> /etc/bashrc on CentOS as well):
>> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
>> Goodbye, world
>>
>> On GuixSD:
>> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
>> Hello, world
>> Goodbye, world
>
> I attached the proposed patch (removing -DSYS_BASHRC).  May I push this
> to core-updates now, or should I wait for the next core-updates cycle?

Not now, because it’s still not merged (but you can help! :-)), but
definitely soonish, hopefully within a few days.

(I think that’s what we agreed on
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29337#28>.)

Thank you!

Ludo’.

  reply	other threads:[~2018-02-09 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 11:39 [bug#30379] [PATCH] gnu: bash: Don't specify default configuration filenames Roel Janssen
2018-02-09 14:06 ` Ludovic Courtès [this message]
2018-03-03 21:55 ` Ludovic Courtès
2018-03-04 14:22   ` Roel Janssen
2018-06-10  5:01 ` bug#30379: Status: " 宋文武

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=87zi4iz288.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30379@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).