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
On Wed, 11 Jun 2003 09:40:24 +0200, Kai Großjohann <[EMAIL PROTECTED]> said:
> Manoj Srivastava <[EMAIL PROTECTED]> writes:
>> A, this is against policy; users need to be able to modify _all_
>> configuration matter.
> But it is not configuration matter. It is simply required for
> getting the
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 pass
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> A, this is against policy; users need to be able to modify
> _all_ configuration matter.
But it is not configuration matter. It is simply required for
getting the package to work at all. It doesn't make sense for users
to remove it or change
A number of suggestions have been made, including some that frob
files in /etc/emacs/site-start.d to check if "their" package is still
installed. IMHO this is the wrong approach.
My suggestion:
* Put files somewhere under /usr that make sure that each package
works, such as via autoloads and s
5 matches
Mail list logo
