Re: Taking over production of emacs20 package.
firstname.lastname@example.org (Christian Lynbech on satellite) writes:
> I think the number one question we need to address is whether we want
> to support running Xemacs and GNU emacs at the *same* time.
The answer is "if it's not an unbelievable technical obstacle, then
yes, we do."
> I do not believe that one can sensibly in the longer *use* both
Think multi-user system.
> If we do, there is probably no way around having the .el files in one
> directory and compile .elc files to another emacs variant specific
> directory. But again, this does not need to be that complicated. One
> could install the .el files in the standard shared directory
> (/usr/share/emacs/site-lisp being my favourite, since this is the
> default location) and then hack the bytecompiler to generate .elc
> files into a subdirectory (say `.emacs-elc' and `.xemacs-elc') and
> finally hack the loader to try the subdirectories first. Don't forget:
> this is emacs, the extensible editor :-)
Right, that's one of the proposals.
> Separate packages such as auctex or cvs, which needs to install elisp
> files, definitely should have one and only one central location to
> stuff things into.
> Requiring all packages to come compiled with both variants is NOT the
> way to go. It will waste diskspace, both on users and for the
> maintainers of packages containing elisp, that now *has* to have both
> variants installed.
That's my feeling.
Rob Browning <email@example.com>
PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .