[
https://issues.apache.org/jira/browse/BIGTOP-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252424#comment-14252424
]
Konstantin Boudnik commented on BIGTOP-1580:
--------------------------------------------
Sorry for being a bit dense: but isn't current approach solves exactly what you
are looking for? {{BIGTOP_BUILD_STAMP}} let you to modify the version of the
package as the JIRA's title says, no? E.g. if one doing multiple iterations of
a package then {{PKG_VERSION}} got increased. {{RELEASE_VERSION}}, on the other
hand, should be used to something that is a property of the software Bigtop
packages. May be I am missing something...?
> Improve Bigtop Toolchain: Versioning of Packages
> ------------------------------------------------
>
> Key: BIGTOP-1580
> URL: https://issues.apache.org/jira/browse/BIGTOP-1580
> Project: Bigtop
> Issue Type: Bug
> Components: build, debian, rpm
> Affects Versions: 0.3.0
> Reporter: Olaf Flebbe
> Fix For: 0.9.0
>
>
> Right now there is no build numbering (beyond -1 ) for different packaging
> attempts and bigtop releases.
> There is no workable way to increase build numbering in Bigtop. (At least
> this is the situation for ubuntu and debian, have not checked RPM).
> This leads to indentical package versions and buildnumbers for different
> bigtop builds when no package version upgrade has been made. This is not
> desirable , since it essentially disables package upgrades at all.
> There is a BIGTOP_BUILD_STAMP which could be used to introduce the needed
> semantics but sadly this BIGTOP_BUILD_STAMP is appended to the PKG_VERSION
> part of the numbering, not the RELEASE_VERSION part .
> I vote to move BIGTOP_BUILD_STAMP to the "right" place in the
> package-version: Appending to RELEASE_VERSION
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
