Dominik 'Rathann' Mierzejewski wrote:
Personally, I use the kernel's recommended commit to the oldest
supported branch and merge upwards workflow and I've learned not to be
afraid of merge commits. If any branch needs some specific fixes,
I just apply them there and only there, without using spec conditionals.
This keeps the specfiles clean and readable, even if they differ
between branches. Obviously, this can't be (easily) automated and
doesn't scale to hundreds or thousands of packages, but it works well
for leaf packages.
rpmautospec doesn't work with the above workflow as it breaks on those
merge commits, produces bogus changelog messages and artificially
inflates Release counters.
This (the failure to handle merge commits) is a serious limitation because
this is one of the workflows where an autochangelog would be most useful, in
order to avoid the merge conflicts on the changelog.
If you work the way I do, avoiding merge commits in favor of fast forwards
and specfile conditionals, then rpmautospec can in principle generate the
autochangelog, but in that case, I do not really need it because my manual
changelog fast-forwards just fine along with the rest of the commit.
Kevin Kofler