From: Ivan Shmakov <ivan@siamics.net>
To: 19564@debbugs.gnu.org
Subject: bug#19564: 24.4; eieio backward compatibility
Date: Tue, 13 Jan 2015 15:27:16 +0000 [thread overview]
Message-ID: <878uh6ya3v.fsf@violet.siamics.net> (raw)
In-Reply-To: <m2lhl6bu7i.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 13 Jan 2015 10:01:37 -0500")
>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
>>>>> On Tue, 13 Jan 2015 15:50:48 +0100 Thierry Volpiatto wrote:
>>>>> Ted Zlatanov <tzz@lifelogs.com> writes:
[…]
TZ> Forgive my ignorance: is that compatibility guaranteed or
TZ> beneficial?
TV> No, but that's mean that now with these recent changes all people
TV> using helm will have errors in their helm packages when switching
TV> emacs-version until they reinstall all; And for sure they will not
TV> reinstall and I expect tons of bugreport in next weeks... (I
TV> crossfingers hoping I am wrong)
TZ> Maybe Emacs needs a shell-level way to recompile all or some
TZ> installed packages?
The approach used in Debian is that the Debian “binary” packages
contain only the source code (.el), and the respective
byte-compiled (.elc) files are produced at the installation
time, – for /each/ of the installed Emacs versions.
So, when, say, gnugo.el is installed, in addition to
/usr/share/emacs/site-lisp/gnugo.el, the following files may
also appear on the filesystem (depending on the versions of
Emacs installed on the system):
/usr/share/emacs25/site-lisp/gnugo.elc
/usr/share/emacs24/site-lisp/gnugo.elc
/usr/share/emacs23/site-lisp/gnugo.elc
…
I’m not sure whether Emacs itself handles it well when it comes
to, say, C-h f. And frankly, for backup purposes, I’d rather
prefer all that to go under /var/cache instead. (And the same
for __pycache__, etc.)
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2015-01-13 15:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 8:03 bug#19564: 24.4; eieio backward compatibility Thierry Volpiatto
2015-01-12 5:08 ` Stefan Monnier
2015-01-12 5:41 ` Thierry Volpiatto
2015-01-12 5:36 ` Stefan Monnier
2015-01-12 5:58 ` Thierry Volpiatto
2015-01-12 7:03 ` Dmitry Gutov
2015-01-12 9:59 ` Thierry Volpiatto
2015-01-12 15:02 ` Stefan Monnier
2015-01-13 8:55 ` Thierry Volpiatto
2015-01-13 12:36 ` Thierry Volpiatto
2015-01-13 14:30 ` Ted Zlatanov
2015-01-13 14:50 ` Thierry Volpiatto
2015-01-13 14:54 ` Dmitry Gutov
2015-01-13 15:13 ` Thierry Volpiatto
2015-01-13 15:01 ` Ted Zlatanov
2015-01-13 15:27 ` Ivan Shmakov [this message]
2015-01-13 16:37 ` Stefan Monnier
2015-01-13 18:06 ` Thierry Volpiatto
2015-01-13 19:52 ` Stefan Monnier
2015-01-14 6:06 ` Thierry Volpiatto
2015-01-14 18:04 ` Stefan Monnier
2015-01-15 5:25 ` Thierry Volpiatto
2015-01-15 15:09 ` Stefan Monnier
2015-01-14 18:05 ` Stefan Monnier
2015-01-15 5:22 ` Thierry Volpiatto
2015-01-15 15:07 ` Stefan Monnier
2015-01-14 19:01 ` Stefan Monnier
2015-01-19 8:48 ` Thierry Volpiatto
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=878uh6ya3v.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=19564@debbugs.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).