From: Stefan Kangas <stefan@marxist.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: GNU ELPA package proposal: visual-fill-column
Date: Tue, 26 Oct 2021 17:17:16 +0200 [thread overview]
Message-ID: <CADwFkm=1BTFtXHVYiqBZV6vKGqfk-ymE2b-haT4CH9xjTCYPxQ@mail.gmail.com> (raw)
In-Reply-To: <jwvlf2fyhew.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> No, `package.el` is not smart enough. The reason is that the version
> numbers used by MELPA don't match the ones used in GNU ELPA, so the
> MELPA versions always seem to be "much higher" than the ones in GNU ELPA
> (e.g. 20180223.223 > 5.7.2).
Maybe we should fix that. Could it be as easy as looking for version
numbers starting with "YYYYMMDD", and if there is no package available
with a version formatted that way, just assume that the currently
highest numbered "normally versioned" package is more recent?
It's easy to think of hypothetical scenarios where it would break, but
it should work for the specific case of GNU ELPA, NonGNU ELPA and
MELPA, at least.
next prev parent reply other threads:[~2021-10-26 15:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 8:38 GNU ELPA package proposal: visual-fill-column Joost Kremers
2021-10-26 13:06 ` Eli Zaretskii
2021-10-26 13:46 ` Michael Heerdegen
2021-10-26 13:47 ` Daniel Martín
2021-10-26 14:17 ` Eli Zaretskii
2021-10-26 17:10 ` Joost Kremers
2021-10-26 14:50 ` Stefan Monnier
2021-10-26 15:17 ` Stefan Kangas [this message]
2021-10-26 15:20 ` Stefan Monnier
2021-10-26 15:29 ` Stefan Kangas
2021-10-26 19:03 ` Philip Kaludercic
2021-11-01 20:27 ` Philip Kaludercic
2021-11-01 21:35 ` Stefan Monnier
2021-11-01 23:39 ` Philip Kaludercic
2021-11-02 2:03 ` Stefan Monnier
2021-11-02 20:52 ` Joost Kremers
2021-11-01 22:23 ` Daniel Martín
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='CADwFkm=1BTFtXHVYiqBZV6vKGqfk-ymE2b-haT4CH9xjTCYPxQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=emacs-devel@gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=monnier@iro.umontreal.ca \
/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).