unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <elpa@tromey.com>
To: "Trent Buck" <trentbuck@gmail.com>
Cc: elpa@tromey.com, emacs-devel@gnu.org
Subject: Re: package.el: bytecode portability across emacs versions
Date: Fri, 25 May 2007 10:00:58 -0600	[thread overview]
Message-ID: <m3zm3s28qt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20070522001139.GA11896@baal.lan> (Trent Buck's message of "Tue\, 22 May 2007 10\:11\:39 +1000")

>>>>> "Trent" == Trent Buck <trentbuck@gmail.com> writes:

Trent> OK, so what file system do you think package.el should use?  Or is it
Trent> also a bad idea to share $HOME across hosts running different Emacs
Trent> releases?

Sorry for the delay in my reply to this.

I know that sharing bytecode is bad.  I just didn't know what to do
about it.

It would be pretty easy to have separate package universes depending
on what Emacs you are running.  But that doesn't seem very
user-friendly.  Putting the bytecode elsewhere could be done but I
gather that this doesn't work too well in some situations.  package.el
could re-byte-compile everything when it detects that you switched
Emacs -- this would be fine for cases like "I upgraded my system and
got a new Emacs", but it would be very unfriendly for other cases.
And of course there's always "don't byte compile at all", but that
would probably rule out installing some of the larger and more
performance-sensitive packages.

Anyway, I'm open to implementing whatever the Emacs experts agree is
the best solution.

Tom

  reply	other threads:[~2007-05-25 16:00 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 [this message]
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=m3zm3s28qt.fsf@fleche.redhat.com \
    --to=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).