From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Nicolas Richard <youngfrog@members.fsf.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Supporting multiline Package-Requires header
Date: Tue, 11 Aug 2015 10:28:16 +0100 [thread overview]
Message-ID: <CAAdUY-JACOW0S7r_4=ddAAnZ8oq5J40Hxcfj=dwFk2pJk=gVog@mail.gmail.com> (raw)
In-Reply-To: <87k2t2b4fd.fsf@members.fsf.org>
2015-08-11 9:44 GMT+01:00 Nicolas Richard <youngfrog@members.fsf.org>:
>>> I understand that the new tools will work with old files, but will the
>>> new files work with the old tools ? i.e. will it be possible to install
>>> these packages to emacs 24.5 ?
>>
>> No. A package that writes it like this will only be (properly) installable on Emacs 25 and up.
>>
>> Of course I'd never drop support for Emacs 24 on one of my packages
>> just for the sake of this minor feature. But once I start routinely
>> requiring Emacs 25.1 because of other features, I'll be glad to have
>> this as a bonus.
>
> It makes sense. My worry is also that emacs-24 must have a way to
> understand that the package is "not installable". e.g. we don't want
> list-packages to suddenly break on older emacsen (I have no idea if this
> can actually happen).
I don't think this can happen. `list-packages' receives information
from the archives, it doesn't manually parse remote packages (it
parses already-installed packages, but if it has been installed
already then it must be compatible). As long as the archive servers
are using the latest Emacs release, they'll know that the package
requires Emacs 25, and they'll provide that information to the user
during `list-packages'.
(And besides, even if the archive is using Emacs 24, or if the user
tries to manually install the package, they'll be immediately greeted
with an error, telling them something is wrong.)
next prev parent reply other threads:[~2015-08-11 9:28 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 11:12 Supporting multiline Package-Requires header Artur Malabarba
2015-08-10 11:42 ` Kaushal
2015-08-10 11:59 ` Artur Malabarba
2015-08-10 12:05 ` Phillip Lord
2015-08-10 12:28 ` Artur Malabarba
2015-08-10 12:51 ` Phillip Lord
2015-08-10 13:08 ` Artur Malabarba
2015-08-10 13:54 ` Bozhidar Batsov
2015-08-10 15:22 ` Artur Malabarba
2015-08-11 21:05 ` Phillip Lord
2015-08-11 21:48 ` Artur Malabarba
2015-08-12 5:34 ` Bozhidar Batsov
2015-08-12 14:09 ` Stefan Monnier
2015-08-12 14:23 ` Artur Malabarba
2015-08-12 17:18 ` Stefan Monnier
2015-08-12 20:10 ` Artur Malabarba
2015-08-13 18:13 ` Artur Malabarba
2015-08-13 20:44 ` Stefan Monnier
2015-08-13 22:37 ` Rasmus
2015-08-13 23:01 ` Artur Malabarba
2015-08-14 0:12 ` Rasmus
2015-08-14 1:42 ` Stefan Monnier
2015-08-17 18:45 ` Achim Gratz
2015-08-18 15:56 ` Stefan Monnier
2015-08-18 18:00 ` Achim Gratz
2015-08-19 17:14 ` Stefan Monnier
2015-08-23 6:33 ` Achim Gratz
2015-08-23 9:17 ` Artur Malabarba
2015-08-23 9:37 ` Achim Gratz
2015-08-23 12:03 ` Artur Malabarba
2015-08-23 22:17 ` Stefan Monnier
2015-08-23 22:12 ` Stefan Monnier
2015-08-23 23:32 ` Artur Malabarba
2015-08-23 22:16 ` Stefan Monnier
2015-08-24 6:56 ` Achim Gratz
2015-08-24 19:17 ` Stefan Monnier
2015-08-24 19:32 ` Achim Gratz
2015-08-24 22:51 ` Artur Malabarba
2015-08-25 5:44 ` Achim Gratz
2015-08-10 14:26 ` Thierry Volpiatto
2015-08-10 15:18 ` Artur Malabarba
2015-08-10 15:38 ` Thierry Volpiatto
2015-08-10 15:53 ` Artur Malabarba
2015-08-10 16:33 ` Thierry Volpiatto
2015-08-10 15:40 ` Nicolas Richard
2015-08-10 15:49 ` Artur Malabarba
2015-08-11 8:44 ` Nicolas Richard
2015-08-11 9:28 ` Artur Malabarba [this message]
2015-08-11 9:33 ` Nicolas Richard
2015-08-10 16:34 ` Thierry Volpiatto
2015-08-10 21:49 ` Phillip Lord
2015-08-11 9:24 ` Artur Malabarba
2015-08-10 22:05 ` Stefan Monnier
2015-08-11 8:56 ` Thierry Volpiatto
2015-08-11 15:55 ` Stefan Monnier
2015-08-10 22:01 ` Stefan Monnier
2015-08-11 9:29 ` Artur Malabarba
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAdUY-JACOW0S7r_4=ddAAnZ8oq5J40Hxcfj=dwFk2pJk=gVog@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=youngfrog@members.fsf.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.