Where does MELPA's package versions come from?

Where does MELPA's package versions come from?

[Stefan Monnier]

E.g. at https://stable.melpa.org/#/camlhttps://github.com/ocaml/caml-mode

I see that the package is released as version 4.7.1 but I can't figure
out where this info comes from: the recipe is

    (caml :repo "ocaml/caml-mode" :fetcher github)

and the code at https://github.com/ocaml/caml-mode doesn't seem to say
"4.7.1" anywhere either.

So where does MELPA find the release version number?


        Stefan

Re: Where does MELPA's package versions come from?

[Clément Pit-Claudel]

> So where does MELPA find the release version number?

It uses git tags.  There has not been a release of caml-mode since the repo moved from ocaml/ocaml to ocaml/caml-mode, so the tag remains from back when the package was in the main ocaml repo.

The move happened in January 2019 (https://github.com/melpa/melpa/commit/d5459264336dec5c94da1e5194dfc4776c8130c7), which is consistent with OCaml being in version 4.07.1 (released Oct 2018, 4.08 was in June 2019).

Clément

On 11/12/20 11:35 PM, Stefan Monnier wrote:
> E.g. at https://stable.melpa.org/#/camlhttps://github.com/ocaml/caml-mode
> 
> I see that the package is released as version 4.7.1 but I can't figure
> out where this info comes from: the recipe is
> 
>     (caml :repo "ocaml/caml-mode" :fetcher github)
> 
> and the code at https://github.com/ocaml/caml-mode doesn't seem to say
> "4.7.1" anywhere either.
> 
> So where does MELPA find the release version number?
> 
> 
>         Stefan
> 
> 

Re: Where does MELPA's package versions come from?

[Basil L. Contovounesios]

Clément Pit-Claudel <cpitclaudel@gmail.com> writes:

>> So where does MELPA find the release version number?
>
> It uses git tags.

That's usually the case for MELPA Stable, right?
I thought MELPA usually uses git HEAD.

-- 
Basil

Re: Where does MELPA's package versions come from?

[Clément Pit-Claudel]

On 11/13/20 8:09 AM, Basil L. Contovounesios wrote:
> Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
> 
>>> So where does MELPA find the release version number?
>>
>> It uses git tags.
> 
> That's usually the case for MELPA Stable, right?
> I thought MELPA usually uses git HEAD.

Correct; Stefan's link was to MELPA stable.  For the regular MELPA the version number is just the date in YYYY.MM.DD format

Re: Where does MELPA's package versions come from?

[Stefan Monnier]

>> So where does MELPA find the release version number?
> It uses git tags.

But there are no tags in that repository!

> There has not been a release of caml-mode since the repo
> moved from ocaml/ocaml to ocaml/caml-mode, so the tag remains from back when
> the package was in the main ocaml repo.

Ahhhhhh!  So the package released as 4.7.1 was build from the previous
repository, which did have a tag "4.7.1".  Gotcha!


        Stefan

Re: Where does MELPA's package versions come from?

[Jean Louis]

* Stefan Monnier <monnier@iro.umontreal.ca> [2020-11-13 07:36]:
> E.g. at https://stable.melpa.org/#/camlhttps://github.com/ocaml/caml-mode
> 
> I see that the package is released as version 4.7.1 but I can't figure
> out where this info comes from: the recipe is
> 
>     (caml :repo "ocaml/caml-mode" :fetcher github)
> 
> and the code at https://github.com/ocaml/caml-mode doesn't seem to say
> "4.7.1" anywhere either.
> 
> So where does MELPA find the release version number?

MELPA does not acknowledge author's version number or convention on
packaging.

It is trying to cope with wrongly written version numbers and uses
probably the date when package was last time fetched from archive. For
example this commithere is from 2nd July 2019 and MELPA injected
automatically package version of 3rd July 2019.

;; Author: Elis "etu" Axelsson
;; URL: https://github.com/etu/0blayout
;; Package-Commit: fd9a8f353dbd45b4628b5f84b8d8c2525ebf571d
;; Package-Version: 20190703.527
;; Package-X-Original-Version: 20160918.0
;; Version: 1.0.2
;; Keywords: convenience, window-management

From MELPA's script package-build.el:

      (with-current-buffer (find-file pkg-target)
        (package-build--update-or-insert-header "Package-Commit" commit)
        (package-build--update-or-insert-header "Package-Version" version)
        (package-build--ensure-ends-here-line pkg-source)
        (write-file pkg-target nil)