unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Trent Buck" <trentbuck@gmail.com>
To: Tom Tromey <elpa@tromey.com>
Cc: emacs-devel@gnu.org
Subject: Re: package.el: bytecode portability across emacs versions
Date: Sat, 26 May 2007 15:33:09 +1000	[thread overview]
Message-ID: <20070526053309.GA28993@baal.lan> (raw)
In-Reply-To: <m3zm3s28qt.fsf@fleche.redhat.com>


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

On Fri, May 25, 2007 at 10:00:58AM -0600, Tom Tromey wrote:
> >>>>> "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?
> 
> I know that sharing bytecode is bad.  I just didn't know what to do
> about it.
> 
> Putting the bytecode elsewhere could be done but I gather that this
> doesn't work too well in some situations.  

On systems with links, you could do something like

    sources/foo-1/foo.el
    21.4/foo-1/foo.el -> ../../sources/foo-1/foo.el
    21.4/foo-1/foo.elc
    23.0.0.1/foo-1/foo.el -> ../../sources/foo-1/foo.el
    22.0.0.1/foo-1/foo.elc

I don't know how well this solves the
sources-should-be-in-the-same-place-as-bytecode issue, because I don't
fully understand the consequences of *not* doing it.  In any case, it
wouldn't work on at least some Windows systems (right?).
-- 
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

  parent reply	other threads:[~2007-05-26  5:33 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 [this message]
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=20070526053309.GA28993@baal.lan \
    --to=trentbuck@gmail.com \
    --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 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).