On November 13, 2006 at 7:41PM -0500, mwolson (at gnu.org) wrote: > Michael Olson <[EMAIL PROTECTED]> writes: > > > I propose adding the following paragraph to the end of Section 9 of > > the debian-emacs-policy document. > > > > If an Emacs add-on package compiles its Emacs Lisp sources, its > > Debian startup script should only add > > /usr/share/<flavour>/site-lisp/<package-name> (and its > > subdirectories of compiled code, if applicable) to the load path, > > rather than /usr/share/<emacs>/site-lisp/<package-name>. If a > > subdirectory of /usr/share/<emacs>/site-lisp/<package-name> contains > > uncompiled Emacs Lisp code, it may also be added to the load path. > > > > I also propose creating a Section 6.E in the same document with the > > following content. > > > > If an Emacs add-on package compiles any of its Emacs Lisp sources, > > it should install the compiled bytecode files to > > /usr/share/<flavour>/site-lisp/<package-name>. It should also > > create a symlink for each Emacs Lisp source file in > > /usr/share/<emacs>/site-lisp/<package-name> and store the symlink in > > /usr/share/<flavour>/site-lisp/<package-name>. If any byte-compiled > > Emacs Lisp code is stored in a subdirectory, similar treatment > > should be used. This ensures that Emacs will be able to locate the > > source code for the add-on package when using M-x find-function and > > similar functionality. > > So, what's the next step for getting these propositions acted on?
Please send the patch to BTS. Bug#122444 and Bug#157123 seem to relate to this issue. #122444: emacsen-common: Please symlink to the .el when byte compiling for each emacsen http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122444 #157123: emacsen-common: policy should require .el files to be in the emacs load-path http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=157123 -- Tatsuya Kinoshita
pgpzk17J9GkQa.pgp
Description: PGP signature
