[Bug 589496] Re: bash --rcfile does not behave as documented

Michael McNeil Forbes 589496 at bugs.launchpad.net
Sun May 28 09:46:20 UTC 2023


What is the status of this?  There is a further discussion from Chet
here:

https://www.mail-archive.com/bug-bash@gnu.org/msg20804.html

Why does Debian enable -DSYS_BASHRC?  This question does not seem to be
answered anywhere.

Is there a workaround?  Can someone release an alternate version of bash
for Ubuntu without -DSYS_BASHRC?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/589496

Title:
  bash --rcfile does not behave as documented

Status in bash package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  New

Bug description:
  Binary package hint: bash

  the bash manpage says this about --rcfile

  --rcfile file
  Execute commands from file instead of the system  wide  initial‐
  ization file /etc/bash.bashrc and the standard personal initial‐
  ization file ~/.bashrc if the shell is interactive (see  INVOCA‐
  TION below).

  under INVOCATION it says

  When  an  interactive  shell that is not a login shell is started, bash
  reads and executes commands from  /etc/bash.bashrc  and  ~/.bashrc,  if
  these  files  exist.  This may be inhibited by using the --norc option.
  The --rcfile file option will force bash to read and  execute  commands
  from file instead of /etc/bash.bashrc and ~/.bashrc.

  but when i execute
  $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall
  it will still read /etc/bash/bashrc (can be verified by adding --verbose)

  using lucid with bash 4.1-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+subscriptions




More information about the foundations-bugs mailing list