Opting into using rpmautospec¶
To opt into using rpmautospec you need to use the two macros as explained here below:
Basically, in the spec file you replace the manually set release, e.g.:
%autorelease macro, such as:
Often, changing to automatic releases will result in an initial jump of the release number
because the number of commits since the last version change is higher than the number of builds
up to here. This is expected and not a sign that the product is defective. To avoid such a jump,
it is best to switch to
%autorelease right before a version bump.
There are different options you can use with this macro which are documented here: Using the %autorelease Macro.
For new packages¶
If you use this macro in a brand-new package without git history, you can simply put the following two lines at the end of your spec file:
From this point on, the build system will insert into your spec file an automatically generated changelog using the information from the git commit history of the package.
For existing packages¶
Existing packages will already have a
%changelog section with some
entries. Those contents should be copied into a
(that will be added to the git repository of the package), and removed
from the spec file. This change must be done in a single commit.
convert command to do this automatically:
After the change, the content of the
%changelog section should be:
From now on, the changelog will be automatically generated from the commit
history of your git repository up until the most recent commit that
More explanations on how the
%autochangelog macro works can be found
in Using the %autochangelog Macro.
Congratulations for opting into rpmautospec. You may now want to have a look at the Peculiarities of rpmautospec.