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

[Rob Browning <rlb@cs.utexas.edu>]

I'm re-copying your entire reply because I put a bogus list name on my
first mail to you (which meant that debian-emacsen wasn't included).

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

> On Sat, Apr 14, 2001 at 06:20:40PM -0500, Rob Browning wrote:
> > To fix this, it seems like maybe we can just change policy (and the
> > relevant emacsXX packages) to reverse the direction of the symlink(s),
> > so then we'd have
> > 
> >   /usr/share/emacs/20.7/site-lisp -> ../emacs20/site-lisp
> > 
> > Does this seem like a suitable solution?
> 
> It's one possibility.  But perhaps a better one is to simply have two
> separate directories: /usr/share/emacs/20.7/site-lisp and
> /usr/share/emacs20/site-lisp, and let them both be in the emacs20
> load-path.
> 
>    Julian

What would be the advantage to two directories?  I guess it would be
less confusing.  I'm wondering if there would be any drawback, though.
Maybe packages accidentally putting files in 20.X/site-lisp rather
than emacs20/site-lisp, though I guess that would just be a bug in the
packages similar to the one we already have.

Anyone else have a reason to prefer one of these solutions over the
other?

Thanks

-- 
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930