unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Trent Buck" <trentbuck@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: elpa@tromey.com, emacs-devel@gnu.org
Subject: Re: package.el: bytecode portability across emacs versions
Date: Sun, 27 May 2007 13:54:54 +1000	[thread overview]
Message-ID: <20070527035454.GB4107@baal.lan> (raw)
In-Reply-To: <E1Hs77Y-0005LA-NY@fencepost.gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]

On Sat, May 26, 2007 at 09:00:32PM -0400, Richard Stallman wrote:
>     I know that sharing bytecode is bad.  I just didn't know what to do
>     about it.
> 
> You could put the bytecode in
> /usr/local/share/emacs/VERSION/site-lisp, which is a standard element
> of load-path, version-specific.  The source code could go in
> /usr/local/share/emacs/site-lisp.  If package.el finds the source
> code and not the binary, it can compile for the current Emacs version.

...except that package.el is (correct me if I'm wrong) intended to be
run by nonpriviledged users, and therefore only $HOME and $TMPDIR are
(typically) writable.

I earlier suggested something like 

    $HOME/.emacs.d/elpa/lisp

for sources, and

    $HOME/.emacs.d/elpa/VERSION

for byte-code, but David suggested this would cause problems.  I
confess I don't quite understand what those problems are.
-- 
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

  reply	other threads:[~2007-05-27  3:54 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
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 [this message]
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=20070527035454.GB4107@baal.lan \
    --to=trentbuck@gmail.com \
    --cc=elpa@tromey.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).