On Wed, 11 Jun 2003 09:45:51 +0200, Kai Großjohann <[EMAIL PROTECTED]> said:
> Manoj Srivastava <[EMAIL PROTECTED]> writes:
>> Sure. Autoloads don't count as configuration in my book either. If
>> that's all you need, then putting the script outside of /etc is
>> fine.
> Good.
>> But load-path modifications are indeed configuration issues,
> Really? It's like passing -R to the linker when linking an
> executable
> -- it just makes sure that the right files are found when starting.
> Do you think that -R args for the linker are configuration issues?
> Semantically, it's the same thing.
I beg to differ. I have two different Gnusii in my load-path
-- and I can change the load-path to use one or the other. Same goes
for bbdb, w3m, and a bunch of other things. The version of bbdb I use
matters a lot to me.
>> as are setting variables at startup.
> I agree. Settings variables should be done from /etc, not /usr.
>> Or creating derived modes on the fly. Or any of the various and
>> sundry things site-start.d scripts do.
> Yes.
> Let's have up to two startup files per package. The one under /usr
> does the non-config stuff, and the one under /etc does the config
> stuff. Often, one of the files will be empty (and thus
> nonexisting).
I really have not seen the benefit of this split. If I have
stuff under /etc I am takling care of anyway, I would rather not
spend effort and code adding yet another directory and files to load
up.
manoj
--
Man's unique agony as a species consists in his perpetual conflict
between the desire to stand out and the need to blend in. Sydney
J. Harris
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
