From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: package-fixes
Date: Sun, 13 Dec 2015 11:44:31 -0500 [thread overview]
Message-ID: <m3zixez4b4.fsf@fitzsim.org> (raw)
In-Reply-To: <CAAdUY-KbzjkcYyHjOKgeGT+d=-hfOGGZemT9e_QFTDR5dVw9gw@mail.gmail.com> (Artur Malabarba's message of "Sun, 13 Dec 2015 10:18:58 +0000")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
> 2015-12-13 2:42 GMT+00:00 Thomas Fitzsimmons <fitzsim@fitzsim.org>:
>> Did you consider making package.el itself a :core package of GNU ELPA,
>> and releasing a fixed package-1.0.2 there?
>
> I did. Sadly, the current package.el is coupled to some built-in
> machinery that wasn't available in 24.1.
> And then there's the question of what will happen if package.el
> upgrades itself in the middle of a transaction (probably nothing
> good). We could make it wait until the end of the transaction to
> upgrade itself, but then it wouldn't prevent the bug in question for
> the package that depended on the newer (package "1.1.0").
OK, too bad. I wonder if at archive-generation time the GNU ELPA build
scripts should insert (package-fixes "<latest version>") in
Package-Requires, for all packages that support emacs < 25.1. It sounds
like it's hard to know if a given package is affected, and even
difficult to replicate a bad-compilation situation?
Someone reported an issue with fsm-0.2.el after upgrading to it, on
Emacs 24.5. I couldn't replicate it. I think it might have been this
issue. I guess once package-fixes lands, to be safe, I should release
fsm-0.3.el that depends on it.
Thomas
prev parent reply other threads:[~2015-12-13 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 23:07 [ELPA] New package: package-fixes Artur Malabarba
2015-12-13 2:42 ` Thomas Fitzsimmons
2015-12-13 10:18 ` Artur Malabarba
2015-12-13 16:44 ` Thomas Fitzsimmons [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=m3zixez4b4.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=bruce.connor.am@gmail.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).