On 12. 08. 20 11:19, Iñaki Ucar wrote:
- Copr newly provides a build-time macro %buildtag. Its format is `.copr<BUILD_ID>` and is useable for auto-incrementing the package's NVR in subsequent builds. It may be used in spec file like: Release: 1%{?dist}%{?buildtag} It could be useful as good-enough alternative for the Release auto-bumping proposal. See the fedora devel discussion [2] for more info. This is not any kind of encouragement to use it. We added it there to easy testing your ideas about the automatic filling of the Release tag.Nice one! I understand that having a mix of builds with and without this tag isn't an issue, right? I.e., would <pkg>-<version>-<release>.copr<id>.fcXX be picked as an update of <pkg>-<version>-<release>.fcXX? Or do we need to rebuild all with the new tag and remove the old ones?
It's actually <pkg>-<version>-<release>.fcXX.copr<id> in the example above. An that sorts higher.
$ rpmdev-vercmp e:v-r.fc34.copr1234567 e:v-r.fc34 e:v-r.fc34.copr1234567 > e:v-r.fc34 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
