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

Re: emacsen: need plan to fix leftover cruft in share/emacs/XX.Y...

On Mon, Jan 22, 2001 at 02:06:28PM -0600, Rob Browning wrote:
> One of the best solutions I've heard so far, dres and debated the
> other night, and that's what I wanted some feedback on.  The idea
> would be to just make it so that /usr/share/emacs20/site-lisp is no
> longer a symlink to /usr/share/emacs/20.7/site-lisp (to use emacs 20.7
> as an example -- same would apply for other emacsen, though), it's a
> real directory, and add-on packages would be required to use that dir.
> This would eliminate the current cruft problem, but raises a couple of
> questions I don't know the answer to ATM:
>   (1) In this situation, should /usr/share/emacs/<version>/site-lisp
>       be a symlink back to /usr/share/emacs/<flavor>/site-lisp i.e.:
(/usr/share/<flavor>/site-lisp you mean)
>       /usr/share/emacs/20.7/site-lisp -> /usr/share/emacs20/site-lisp?

Surely you don't need to do this; just add
/usr/share/<flavor>/site-lisp to the library path in the <flavor>
startup files.  But on second thoughts, add-on packages expect this
directory to exist, so I guess it will have to.

>   (2) Will this cause nasty problems during the package upgrade
>       process between two minor versions, i.e. 20.6 -> 20.7,
>       including, but not limited to problems caused if/when backwards
>       .elc file compatibility is broken?

Hopefully not.  Bug if it does.

> I think it's at least possible that this would work right as long as
> emacsen-common is *really* careful to call the add-on package removal
> scripts when the old (20.6) package is being removed, and the add-on
> packages are *really* careful to clean up anything that could cause
> the new version (20.7) to retch.

Sounds good; bug if the package doesn't do this.

> Does this sound feasible?  If so, I think it's a lot better than what

I think it's good, as long as we figure out a way to cleanly upgrade
from the current system to the new one, as there are going to problems
with dpkg otherwise; I guess removing the current
/usr/share/<flavor>/site-lisp symlink in the emacs20 preinst should do
the job:
  [ -L /usr/share/$flavor/site-lisp ] && rm -f /usr/share/$flavor/site-lisp



         Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
       Debian GNU/Linux Developer,  see http://people.debian.org/~jdg
  Donate free food to the world's hungry: see http://www.thehungersite.com/

Reply to: