From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
Stefan Kangas <stefan@marxist.se>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: GNU ELPA package proposal: visual-fill-column
Date: Tue, 26 Oct 2021 19:03:33 +0000 [thread overview]
Message-ID: <87cznrk3qy.fsf@posteo.net> (raw)
In-Reply-To: <jwva6ivyfum.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 26 Oct 2021 11:20:54 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Stefan Kangas [2021-10-26 17:17:16] wrote:
>> 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?
>
> Assuming would definitely not be a good idea because scenarios where
> this is a bad idea aren't sufficiently hypothetical, IMO.
Yes, there are packages on both GNU and NonGNU ELPA that use this as
their stable versioning scheme.
> But we could add a hack that would detect such cases are prompt the user.
How about introducing a package header to indicate that the versioning
scheme, so that package.el can fix it?
> Better if we could get the release date of the package version 5.7.2 ;-)
>
>
> Stefan
--
Philip Kaludercic
next prev parent reply other threads:[~2021-10-26 19:03 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
2021-10-26 15:20 ` Stefan Monnier
2021-10-26 15:29 ` Stefan Kangas
2021-10-26 19:03 ` Philip Kaludercic [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cznrk3qy.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.