Re: /etc/bash.bashrc derivation and "misuses"

2007-02-25 Thread Chet Ramey
Linda Walsh wrote:
> 
> 
> Chet Ramey wrote:
>> not a standard part of the build, so it's not in the man page.
>> Putting a mention of it in would cause more problems that it would solve.
> ---
> Maybe, but a mention of it might not.  Some verbiage that some
> implementations
> of bash "may implement a system-wide 'bashrc' equivalent, that by default,
> is called '/etc/bash.bashrc'.  More information is available in the
> source".

That's not appropriate for a man page.  In my opinion, if a system vendor
chooses to enable that sort of functionality (and many do, for all sorts
of reasons), then they need to add something to the documentation noting
that.  It doesn't have to be complicated:

/etc/bash.bashrcSystem-wide interactive shell initialization file

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
   Live Strong.  No day but today.
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: /etc/bash.bashrc derivation and "misuses"

2007-02-25 Thread Paul Jarc
Chet Ramey <[EMAIL PROTECTED]> wrote:
> In my opinion, if a system vendor chooses to enable that sort of
> functionality (and many do, for all sorts of reasons), then they
> need to add something to the documentation noting that.

Could that be done automatically by ./configure when this is enabled?


paul


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: /etc/bash.bashrc derivation and "misuses"

2007-02-25 Thread Chet Ramey
Paul Jarc wrote:
> Chet Ramey <[EMAIL PROTECTED]> wrote:
>> In my opinion, if a system vendor chooses to enable that sort of
>> functionality (and many do, for all sorts of reasons), then they
>> need to add something to the documentation noting that.
> 
> Could that be done automatically by ./configure when this is enabled?

It's not controlled by configure; it's a define that needs to be
modified manually in config-top.h.  The fact that you have to edit a
header file by hand and enable it is intended to indicate that some
other work is required.  Maybe a note in config-top.h is needed.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
   Live Strong.  No day but today.
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash