On Mon, Jan 13, 2020 at 08:19:36AM -0600, Richard Shaw wrote:
Just catching up on this thread...
How about an incremental step? (I don't know how difficult it would be to
implement however)...
What about separating the change log to a separate file in dist-git?
Something like the traditional "ChangeLog"?
I like to keep my spec files in sync between releases unless there's a good
reason for them to diverge but sometimes there are changes to a specific
release that aren't really a part of the others.
That way I can keep the spec files in sync (git merge master, et. all) but
without merging changelogs that don't actually apply to that release (and
dealing with merge conflicts)?
I do a variant of this with rpminspect and some other packages. I
automatically generate 'changelog' when I make a new upstream release. This
and the tarball then Source0 and Source1. The spec file has:
%changelog
%include %{SOURCE1}
I don't upload the changelog to the lookaside cache, but just commit it in
dist-git. I'm trying to strictly release from upstream and push builds in to
dist-git, but I'm doing this changelog structure so that if there is
downstream maintenance needed them commits to the changelog can be separate
from spec and patch changes which makes cherry-picking across branches
theoretically easier.
There is the problem of Release, which I would like to have in a separate file
to that I can also %include. Haven't tried that yet mostly because I haven't
had an excuse to.
Thanks,
--
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat, Inc. | Boston, MA | EST5EDT
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
