Skip to content
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.

Add logic to extend or override the Version and Release tags for GitArchive resources #509

Open
euanh opened this issue Mar 27, 2018 · 1 comment

Comments

@euanh
Copy link
Contributor

euanh commented Mar 27, 2018

When we build a package from pinned sources (usually a developer or development branch build), we currently use the version and release from the spec file. This means that, although the package has been built from untagged sources, the resulting package will have same NEVRA as the most recent tagged, released build. We should append some data (derived from git describe) to the version or release (whichever is appropriate) to distinguish a pinned package from a released one. If we format it correctly, this will even allow yum and dnf to upgrade from a release version to a development version, from a development version to another development version, and even from a development version to the next release version.

@mseri
Copy link
Contributor

mseri commented May 2, 2018

Removed from pinning v3 as this is now planned as planex-4.1.0 or planex-4.2.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants