Tobias Klauser wrote: > On 2007-06-06 at 09:38:49 +0200, Josh Triplett <[EMAIL PROTECTED]> wrote: >> Package: cscope >> Version: 15.6-2 >> Severity: normal >> File: /etc/emacs/site-start.d/50cscope.el >> >> The emacs startup file /etc/emacs/site-start.d/50cscope.el requires xcscope. >> Emacs startup files for packages should not make invasive changes; generally >> they shouldn't do anything more invasive than an autoload and an >> auto-mode-alist entry. Any emacs user who wants to use xcscope can easily >> add >> the require line to their .emacs, just as they do for any other emacs package >> in Debian. >> >> (require 'xcscope nil t) works nicely if you don't want your .emacs to break >> if it can't find xcscope. > > I'm not using emacs myself and do not really have much experience > with it, so I don't really know, what the best solution would be here. > > My current solution would be to not install the startup file and maybe > add a note to the changelog (or even NEWS) about this change, so users > relying on the current behaviour would be informed to change their > setup. > > What do you think?
That seems reasonable. Normally, a package would need a startup file to add their path to the emacs load-path; however, cscope just puts its only file directly in the site-lisp directory. That seems somewhat reasonable, though I don't know if it follows the letter of the Debian Emacs policy. I also notice that cscope doesn't seem to byte-compile its elisp. This slows down load time. That represents a separate problem, though. - Josh Triplett
signature.asc
Description: OpenPGP digital signature
