From: David Kastrup <dak@gnu.org>
To: "Trent Buck" <trentbuck@gmail.com>
Cc: elpa@tromey.com, emacs-devel@gnu.org
Subject: Re: package.el: bytecode portability across emacs versions
Date: Mon, 21 May 2007 20:10:47 +0200 [thread overview]
Message-ID: <85veemdp3s.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20070521134747.GA14137@baal.lan> (Trent Buck's message of "Mon\, 21 May 2007 23\:47\:47 +1000")
"Trent Buck" <trentbuck@gmail.com> writes:
> Arbitrary emacs lisp cannot be byte-compiled in one version of Emacs
> and loaded in another, as the following transcript shows:
[...]
> This is most obvious in the wild in emacs-w3m, but I've had problems
> with other packages also.
>
> package.el appears to create bytecode in a common directory.
It creates the bytecode in the directory where the source Elisp files
lie, I would presume.
> Unless code is carefully audited, any time .emacs.d is shared
> between multiple emacsen packages errors can be expected.
Sharing such a directory is a mistake, anyway.
> Recommendation: either 0) tell users not to run more than one emacs;
> 1) don't byte-compile; or 2) place bytecode in path(s) local to the
> current emacs-version.
>
> Debian's elisp package framework adopts (2), that might be a source of
> inspiration.
Debian's Elisp package framework socks boulders through straws. Emacs
is designed to have Elisp and elc files in the same directory. That's
how load-path orders can take effect. Debian completely breaks this,
as witnessed by calling M-x list-load-path-shadows RET. And, of
course, things like M-x byte-recompile-directory RET don't work in
Debian, either.
Sharing Elisp files between different Emacs variants is not a good
idea.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-05-21 18:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:47 package.el: bytecode portability across emacs versions Trent Buck
2007-05-21 18:10 ` David Kastrup [this message]
2007-05-21 23:01 ` Kevin Ryde
2007-05-22 0:11 ` Trent Buck
2007-05-25 16:00 ` Tom Tromey
2007-05-26 1:32 ` Michael Olson
2007-05-26 6:34 ` David Kastrup
2007-05-26 10:34 ` Eli Zaretskii
2007-05-26 10:40 ` David Kastrup
2007-05-26 5:33 ` Trent Buck
2007-05-26 6:02 ` Eli Zaretskii
2007-05-27 1:00 ` Richard Stallman
2007-05-27 3:54 ` Trent Buck
2007-05-27 5:41 ` David Kastrup
2007-05-27 23:21 ` Richard Stallman
2007-05-28 6:33 ` David Kastrup
2007-05-29 0:02 ` Richard Stallman
2007-05-30 0:44 ` Michael Olson
2007-05-30 15:44 ` Richard Stallman
2007-05-28 21:35 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85veemdp3s.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=elpa@tromey.com \
--cc=emacs-devel@gnu.org \
--cc=trentbuck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).