From: bruce.connor.am@gmail.com
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Elpa packages and macro dependencies.
Date: Fri, 17 Oct 2014 09:39:30 +0100 [thread overview]
Message-ID: <CAAdUY-Jf2P2q0xz=OODvUJfPw6Etha+GyOqEoJC95BaFrTCaow@mail.gmail.com> (raw)
In-Reply-To: <8761fjsp2c.fsf@Rainer.invalid>
Achim Gratz:
> That doesn't work when defcustoms, autoloads and defvars change in the
> new version.
It would be good to fix autoloads indeed, but you can't force-reload
defcustoms, or you'll be erasing user customizations.
You could reload them only if its value is still the standard value,
but then users who has customized it would still run into the same
problem.
That said, IIUC, defcustoms and defvars aren't really a huge problem.
They're only problematic if the package author changes something in a
backwards-incompatible way (thus making an old defcustom not work with
new code). And even then, things should resume normality after a restart.
Or am I missing something?
The problem with macros is that they break installation of packages,
and it happens even if all package authors respect backwards
compatibility.
prev parent reply other threads:[~2014-10-17 8:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 16:06 Elpa packages and macro dependencies bruce.connor.am
2014-10-16 16:09 ` Glenn Morris
2014-10-16 16:56 ` bruce.connor.am
2014-10-16 16:59 ` Thierry Volpiatto
2014-10-16 17:44 ` Stefan Monnier
2014-10-16 17:57 ` bruce.connor.am
2014-10-16 19:57 ` Stefan Monnier
2014-10-17 8:28 ` bruce.connor.am
2014-10-17 15:54 ` bruce.connor.am
2014-10-17 16:36 ` Stefan Monnier
2014-10-17 21:24 ` bruce.connor.am
2014-10-18 21:41 ` Stefan Monnier
2014-10-20 8:58 ` Nicolas Richard
2014-10-20 9:33 ` Artur Malabarba
2014-10-20 19:04 ` Stefan Monnier
2014-10-20 20:25 ` Artur Malabarba
2014-10-20 20:40 ` Stefan Monnier
2014-11-13 11:57 ` Artur Malabarba
2014-11-13 17:34 ` Stefan Monnier
2014-12-10 18:38 ` Artur Malabarba
2014-12-10 19:14 ` Stefan Monnier
2014-10-19 6:57 ` Achim Gratz
2014-10-20 15:29 ` Stefan Monnier
2014-10-20 16:34 ` Achim Gratz
2014-10-20 18:00 ` Stefan Monnier
2014-10-20 19:16 ` Achim Gratz
2014-10-20 21:04 ` Stefan Monnier
2014-10-21 17:41 ` Achim Gratz
2014-10-16 21:05 ` Achim Gratz
2014-10-17 3:03 ` Stefan Monnier
2014-10-17 8:01 ` Achim Gratz
2014-10-17 12:03 ` Phillip Lord
2014-10-17 13:51 ` Tom Tromey
2014-10-17 12:39 ` Stefan Monnier
2014-10-17 8:39 ` bruce.connor.am [this message]
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='CAAdUY-Jf2P2q0xz=OODvUJfPw6Etha+GyOqEoJC95BaFrTCaow@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=Stromeko@nexgo.de \
--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).