Re: Bug#61167: emacsen-common: major bug in policy (not RC for potato)

[Rob Browning <rlb@defaultvalue.org>]

Julian Gilbey <J.D.Gilbey@qmw.ac.uk> writes:

> Here's another suggestion.  Why not leave the existing emacsen
> packages as they are and apply the rule only to new versions of
> emacs (so emacs21 and xemacs22 onwards)?  That will save the hassle,
> I guess.

Thanks for the suggestion.  That sounded like the right thing to me.
Accordingly, after consulting with dres, I've modified
debian-emacs-policy to fix the problem.  However, the emacs20 packages
may never be fixed, but the emacs21 packages will be fixed upon first
release.

Here's the relevant text from the upcoming emacsen-common policy.

  /usr/share/<flavor>/site-lisp should be used instead of the normal
  site-lisp directory for that flavor of emacs.  In addition, the
  package for a given flavor of emacs should not have the normal
  site-lisp directory.  For example, instead of the emacs20 package
  having /usr/share/emacs/20.7/site-lisp, it should only have
  /usr/share/emacs20/site-lisp.  This is important because it allows
  us to avoid having dangling directories for old versions across
  upgrades.  We could have chosen to keep a compatibility symlink, but
  that seemed likely to mask bugs in the debianized packages.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD