Re: Bug#193439: emacsen-common: debian-emacs-policy and package setup in conffile
Manoj Srivastava <srivasta@debian.org> 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.
> 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).
--
This line is not blank.
Reply to: