Re: replacing packages
In article <firstname.lastname@example.org>, James LewisMoss <email@example.com> writes:
> OK I've deprecated the xemacs19 packages leaving only the xemacs20
> packages (the xemacs20-nomule package is equivalent to the xemacs19
> package and has newer el files, is more stable, and is faster to
> OK so now the problem with disappearing packages has appeared. Is
> there any way to make the xemacs20 packages replace the xemacs19
> packages in dselect (or whatever) so that the user doesn't have to
> think about it? I'm guessing there isn't since I've seen similar
> discussions before, but before I tell this person there's not a lot
> I can do I wanted to check to make sure I was correct.
Replaces/conflicts is the best you can do.
Are you really sure this isn't good enough? What about a user, lets
call him 'Jonam', which has 23 MB of emacs lisp tuned to xemacs19 ?
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>