On Wed, Jan 15, 2020 at 7:10 AM Miroslav Suchý <msuchy(a)redhat.com> wrote:
Dne 11. 01. 20 v 3:54 Neal Gompa napsal(a):
> * %{dist}.<commit-at-version>.<build-at-version>
-1
Packages with commitish in release version are usually developers snapshot.
We already have few packages with such release in Fedora, but I would dislike to make
this standard.
That is not putting the hash in there. That is a counter. It's poorly labeled.
Basically, an NEVRA would look like this:
foo-0:1.0.0-fc32.1.1.noarch
"commit-at-version" is a counter, starting from 1 that indicates the
number of commits in the build system of the version of a package. So
version 1.1 would start at 1 initially, and every subsequent commit
where you _don't_ change the version, this number goes up.
"build-at-version" is a counter, starting from 1 that indicates the
number of builds in the build system of the commit at that version of
a package. So at version 1.1 with commit-at-version 1 would initially
have build-at-version 1 for the first build, but on the fourth
rebuild, it would be 5.
Given that, here's what the options I presented would look like the
following Release fields:
* <commit-at-version>%{dist}.<build-at-version>: 1.fc32.5
* <commit-at-version>.<build-at-version>%{?dist}: 1.5.fc32
* %{dist}.<commit-at-version>.<build-at-version>: fc32.1.5
--
真実はいつも一つ!/ Always, there's only one truth!