From: Michael Olson <mwolson@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: package.el: bytecode portability across emacs versions
Date: Tue, 29 May 2007 20:44:38 -0400 [thread overview]
Message-ID: <87wsyrxhqh.fsf@hariken.mwolson.org> (raw)
In-Reply-To: 85tztyrfgu.fsf@lola.goethe.zz
[-- Attachment #1.1: Type: text/plain, Size: 1614 bytes --]
David Kastrup <dak@gnu.org> writes:
> Richard Stallman <rms@gnu.org> writes:
>
>> 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.
>
> Emacs is not well-equipped to have source and byte code in different
> directories. For example, it messes with the load path order: Emacs
> will prefer loading an .el file in an earlier place in the load-path
> over a .elc file in a later place.
>
> It also stops byte-recompile-directory from working and makes
> list-load-path-shadow complain.
>
> I don't say that such a system could not be supported, but it would
> need code changes outside of package.el itself.
If you put symlinks to the source files in the same directory as the
byte-compiled files (or just copy them there), and don't include the
version-independent directory in load-path, there is no problem (to the
best of my knowledge). I'm trying to get something to this effect added
to the Debian Emacs packaging policy, but the policy-makers are rather
slow.
--
Michael Olson -- FSF Associate Member #652 |
http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | |
Sysadmin -- Hobbies: Lisp, GP2X, HCoop | |_] | \| |_|
Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |
[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 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-30 0:44 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
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 [this message]
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=87wsyrxhqh.fsf@hariken.mwolson.org \
--to=mwolson@gnu.org \
--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).