From: "Trent Buck" <trentbuck@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: elpa@tromey.com, emacs-devel@gnu.org
Subject: Re: package.el: bytecode portability across emacs versions
Date: Tue, 22 May 2007 10:11:39 +1000 [thread overview]
Message-ID: <20070522001139.GA11896@baal.lan> (raw)
In-Reply-To: <85veemdp3s.fsf@lola.goethe.zz>
[-- Attachment #1.1: Type: text/plain, Size: 1429 bytes --]
On Mon, May 21, 2007 at 08:10:47PM +0200, David Kastrup wrote:
> "Trent Buck" <trentbuck@gmail.com> writes:
> > 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.
Forgive me, I did not know.
> > 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.
Correct.
> > 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.
>
> [...]
>
> Sharing Elisp files between different Emacs variants is not a good
> idea.
OK, so what file system do you think package.el should use? Or is it
also a bad idea to share $HOME across hosts running different Emacs
releases?
--
Trent Buck
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2007-05-22 0:11 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
2007-05-21 23:01 ` Kevin Ryde
2007-05-22 0:11 ` Trent Buck [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070522001139.GA11896@baal.lan \
--to=trentbuck@gmail.com \
--cc=dak@gnu.org \
--cc=elpa@tromey.com \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.