On 19.05.05 Florent Rougon ([EMAIL PROTECTED]) wrote:
> Juhapekka Tolvanen <[EMAIL PROTECTED]> wrote:
Hi,
> > Setting up tetex-bin (2.0.2-30) ...
> > /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
>
> [...]
>
> IMHO, the bug is in your bash setup that runs .bashrc for every script.
> .bashrc is for interactive shells that are not login shells, as
> documented in bash(1).
>
BASH_ENV
If this parameter is set when bash is executing a shell
script, its value is interpreted as a filename
containing commands to initialize the shell, as in
~/.bashrc. The value of BASH_ENV is subjected to
parameter expansion, command substitution, and
arithmetic expansion before being interpreted as a file
name. PATH is not used to search for the resultant
file name.
Would it make sense to unset BASH_ENV too?
> If scripts started to read .bashrc files everywhere, we'd have a
> lot of problems since you should define your aliases and functions
> there, IIRC.
>
Correct. In my .bashrc I have an alias for rm (rm -i), nevertheless I
expect an rm call in a shell script to be executed without asking.
H.
--
sigmentation fault
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
