Re: Bug#61167: emacsen-common: major bug in policy (not RC for potato)
- To: Julian Gilbey <J.D.Gilbey@qmw.ac.uk>
- Cc: firstname.lastname@example.org, email@example.com
- Subject: Re: Bug#61167: emacsen-common: major bug in policy (not RC for potato)
- From: Rob Browning <firstname.lastname@example.org>
- Date: 17 Jul 2001 11:11:34 -0500
- Message-id: <email@example.com>
- In-reply-to: <20010705232835.A3985@polya>
- References: <20010402115358.A29457@polya> <firstname.lastname@example.org> <20010402165938.A29800@polya> <email@example.com> <20010416023611.A29393@polya> <firstname.lastname@example.org> <email@example.com> <20010521215455.F6370@polya> <firstname.lastname@example.org> <20010705232835.A3985@polya>
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
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.
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD