Re: emacsen: need plan to fix leftover cruft in share/emacs/XX.Y...
>>>>> On 25 Jan 2001 11:08:48 -0600, Rob Browning <rlb@cs.utexas.edu> said:
Rob> Peter S Galbraith <GalbraithP@dfo-mpo.gc.ca> writes:
>> Look, you'll the emacs maintainer, so you should know, which means
>> I'm probably wrong and should test it before I go on. But even
>> going from, say, 20.2 to 20.7, when emacs-20.2 is removed the
>> emacsen-remove scripts get called and cruft gets deleted. Then
>> emacs-20.7 is installed and cruft (compilation logs) are recreated
>> in a different place. The only problem is that the add-on
>> package-supplied emacsen-remove scripts didn't clean up the
>> compilation logs correctly.
Rob> OK, you and I were miscommunicating on this point. When you
Rob> said emacsen-remove scripts the first time, I thought you'd
Rob> meant I should add code to the scripts *in* emacsen-common, when
Rob> it looks like what you really meant was the removal scripts in
Rob> the add-on packages. Given that, I think you're right on this
Rob> point.
Rob> So the only point we haven't resolved is whether or not add-on
Rob> packages should clean up old-cruft, or just be expected not to
Rob> generate future cruft.
IMO. They should be required to clean up old cruft as well. The
only problem here is that there will still be stuff left around. For
example:
/usr/share/emacs/20.3/:
etc
site-lisp
/usr/share/emacs/20.3/etc:
bbdb
/usr/share/emacs/20.3/etc/bbdb:
tex
utils
/usr/share/emacs/20.3/etc/bbdb/tex:
bbdb-cols.tex
bbdb-print-brief.tex
bbdb-print.tex
/usr/share/emacs/20.3/etc/bbdb/utils:
bbdb-213-310.el
bbdb-415-510.el
bbdb-areacode-split.pl
bbdb-cid.pl
bbdb-srv.pl
bbdb-to-netscape.el
bbdb-unlazy-lock.pl
/usr/share/emacs/20.3/site-lisp:
debview
python-elisp
/usr/share/emacs/20.3/site-lisp/debview:
install.log
/usr/share/emacs/20.3/site-lisp/python-elisp:
install.log
python-mode.elc
If bbdb cleans up the files it put in etc/bbdb the dir etc will still
exist and if debview and python-elisp cleanup the files from site-lisp
the site-lisp dir will still be around. and in both cases the 20.3 dir
will still be around.
Solutions I see:
1) emacsen-common itself cleans up there particular dirs.
2) each elisp package tries to cleanup all these dirs and ignores a
failure (something else is still there).
For the files themselves and the dirs they create I think that elisp
packages should be required to clean up their old cruft as well.
Jim
--
@James LewisMoss <dres@debian.org> | Blessed Be!
@ http://jimdres.home.mindspring.com | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
Reply to: