From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Yoni Rabkin <yoni@rabkins.net>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: version numbers in ELPA
Date: Thu, 18 Feb 2021 10:41:25 +0100 [thread overview]
Message-ID: <875z2paf22.fsf@gmx.de> (raw)
In-Reply-To: <jwva6s2fw42.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 17 Feb 2021 12:30:50 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Yes, version numbers are defined in ELPA (notice: not "GNU ELPA" but
> "ELPA") as sequences of numbers. Since 1 and 01 are one and the same
> number, then ... 2.01 is the same as 2.1.
>
>> Are there some implicit rules to follow as to how we should number
>> versions going to ELPA? Are there some explicit rules I just skimmed
>> over and didn't take note of?
>
> Yes, the version numbers need to obey `version-to-list` and the actual
> string used to represent the version number in the name of the tarball
> need to be "canonicalized" by passing them to `version-to-list` and then
> recreating a corresponding string out of it with `package-version-join`
> (defined in `package.el`). This need is because the `archive-contents`
> file (which lists the tarballs available in a given ELPA server) give
> the versions in the form of a list of numbers rather than a string, and
> then `package.el` needs to "guess" the name of the corresponding tarball
> by creating a string out of it.
Perhaps we can recommend semantic versioning <https://semver.org/>? This
speaks also about the syntax, leading zeroes are forbidden ("MUST NOT").
`version-to-list' seems to be close to this, but I haven't checked for
differences.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2021-02-18 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 17:11 version numbers in ELPA Yoni Rabkin
2021-02-17 17:30 ` Stefan Monnier
2021-02-17 17:34 ` Yoni Rabkin
2021-02-18 9:41 ` Michael Albinus [this message]
2021-02-17 23:28 ` chad
2021-02-17 23:51 ` Yoni Rabkin
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=875z2paf22.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yoni@rabkins.net \
/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.