Re: Bug#193439: emacsen-common: debian-emacs-policy and package setup in conffile
On Mon, 19 May 2003 20:04:14 -0400, Peter S Galbraith <email@example.com> said:
> Manoj Srivastava <firstname.lastname@example.org> wrote:
>> On Fri, 16 May 2003 11:54:52 -0400, Peter S Galbraith
>> <email@example.com> said:
>> > Simon Josefsson <firstname.lastname@example.org> wrote:
>> >> One solution would be to modify emacs to look for, before
>> >> default.el and site-start.el, a /usr/share/emacs/debian-lisp.el
>> >> and have a /usr/share/emacs/debian-lisp.rc/ directory which
>> >> corresponds to todays' /etc/emacs/site-start.d/ but is managed
>> >> entirely by Debian packages. The files should contain the
>> >> minimal amount of code required to get a package up'n'running,
>> >> and should assume the rest of the package is installed.
The question is whether there is anything in this "minimal
amount of code" anything that can be considered configuration
information. If the package would not start or run without some
changes, then the package needs be patched to work with debian -- you
do not need start up time hacks to get around needed changes in the
package. Now, changing package configuration to make it better suited
for Debian, yes, I can see the need for startup scripts doing that
(optionally, of course, controlled by the user).
Load paths and autoloads are the other common things packages
seem to do. I should be able to prevent that without having to remove
the package it self (for example, if only some of my users use a
package, and it interferes with others, I can comment out the path
enhancement in /etc/emacs/site-start.d/blah; and only do the changes
in my ~/.emacs. I contend that modification of my emacs load-path
_is_ a configuration change, since the load-path is something I think
of as a configuration variable. Don't you?
The file serves as example code of the changes I need make in
>> >> Then /etc/emacs/site-start.d/ can be dedicated entirely to site
>> >> customizations, instead of being something where debian packages
>> >> write to but is unable to modify or remove in.
Umm. You can indeed modify things, as long as user changes are
>> Then you better start getting policy changed.
> You mean emacs-policy? That's not such a big thing, is it?
If files in /usr/share/emacs/debian-lisp.rc/ directory contain
configuration information, then that violates general debian policy.
As flies to wanton boys are we to the gods; they kill us for their
sport. Shakespeare, "King Lear"
Manoj Srivastava <email@example.com> <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