Learn more about these different git repos.
Other Git URLs
Some more-complicated packages (such as nodejs) use the special %global variable baserelease to set the release number so it can be reused in other places. I'd like to be able to set this as %autorelease:
nodejs
%global
baserelease
%autorelease
%global baserelease %{autorelease}
In the Node.js case, the use of %baserelease exists to provide a special release tag for its subpackages to ensure that they upgrade with the main nodejs package. For example, npm has the ENVR 1:npm-8.12.1-1.18.4.0.1 indicating that it is version 8.12.1, associated with 1:nodejs-18.4.0-1.
%baserelease
npm
1:npm-8.12.1-1.18.4.0.1
1:nodejs-18.4.0-1
@sgallagh, hmm, %autorelease is a normal parametrized macro (unlike %autochangelog) so I take it you’re asking for a flag to suppress %{?dist} being added to it? E.g. if I added an option -n to it which would do that, you could do:
%autochangelog
%{?dist}
-n
... %global baserelease %{autorelease -n} ... %global nodejs_release %{baserelease} ... %global v8_release %{nodejs_epoch}.%{nodejs_major}.%{nodejs_minor}.%{nodejs_patch}.%{nodejs_release} ... %global npm_release %{nodejs_epoch}.%{nodejs_major}.%{nodejs_minor}.%{nodejs_patch}.%{nodejs_release} ... Release: %{nodejs_release}%{?dist} ... %package -n v8-devel ... Release: %{v8_release}%{?dist} ... %package -n npm ... Release: %{npm_release}%{?dist} ...
NB: Just realized, the way you use it, you could should be able to use the existing macro in %baserelease and drop %{?dist} below.
Metadata Update from @nphilipp: - Issue tagged with: Needs Deployment, Release Bumping Functionality
Metadata Update from @nphilipp: - Issue untagged with: Release Bumping Functionality
Metadata Update from @nphilipp: - Issue set to the milestone: 0.3
Metadata Update from @nphilipp: - Issue tagged with: Documentation
Metadata Update from @nphilipp: - Issue assigned to nphilipp
Commit 52f3c20 fixes this issue
Log in to comment on this ticket.