[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: A flaw in current emacsen package setup?

* Manoj Srivastava 

| 	Perhaps add-after-local (or a renamed version of the function)
|  should be provided by default, and policy changed to recommend the
|  use of that function.

This seems like a good solution to me.

| 	I am copying this message to all packages currently violating
|  the emacsen policy on load-paths. Please consider this fair warning
|  for serious bugs to be filed when we reach a solution of this issue.

File a bug against dh-make as well, since from one of it's templates
in /usr/share/debhelper/dh_make/debian/emacsen-startup.ex:

;; -*-emacs-lisp-*-
;; Emacs startup file for the Debian GNU/Linux #PACKAGE# package
;; Originally contributed by Nils Naumann <naumann@unileoben.ac.at>
;; Modified by Dirk Eddelbuettel <edd@debian.org>
;; Adapted for dh-make by Jim Van Zandt <jrv@vanzandt.mv.com>

;; The #PACKAGE# package follows the Debian/GNU Linux 'emacsen' policy and
;; byte-compiles its elisp files for each 'emacs flavor' (emacs19,
;; xemacs19, emacs20, xemacs20...).  The compiled code is then
;; installed in a subdirectory of the respective site-lisp directory.
;; We have to add this to the load-path:
(setq load-path (cons (concat "/usr/share/"
                              (symbol-name flavor)
			      "/site-lisp/#PACKAGE#") load-path))

I think much of the problems stems from the fact that dh-make includes
this template.


Tollef Fog Heen
Axiom #1: You Can't Win

Reply to: