[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bash-bug
Subject:    Re: Feature discussion - startup files
From:       Chet Ramey <chet.ramey () case ! edu>
Date:       2015-12-23 14:51:51
Message-ID: 567AB507.8050202 () case ! edu
[Download RAW message or body]

On 12/21/15 6:17 PM, Ángel González wrote:
> Chet Ramey wrote:
>> The current configurable startup file options are insufficient for
>> their purposes because they can be enabled or disabled by vendors,
>> and these folks would rather not modify the "vendor" parts of the
>> system. In some cases, with some Linux distributions, doing so voids
>> their support.
> 
> How are they going to deal with vendors disabling the new configuration
> file, too?

The idea is that by making it an unconditional option that is on by
default, vendors will be discouraged from changing it.  It's an
optimistic perspective, no doubt.

> "Create a new configuration file" is the wrong "solution" to "the
> vendor disables existing configuration files".

As I said, the vendor is the obstacle here.  (And it's not `the vendor',
its the multitude of them that make different choices.)

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/


[prev in list] [next in list] [prev in thread] [next in thread]