On 14. 02. 21 19:45, Kevin Fenzi wrote:
So, I am a bit leary of this change for the same reason that I was for
the last few changes like this. Namely, we are building out own layer on
top of rpm to make our lives easier, when we probibly should try and
just improve rpm to do this for everyone.
I realize that rpm is slow to move and this might not be practical, but
I sure wish we would try.
As a strawman, what about this that upstream might take:
* keep the same macros you propose (don't care what colour the bikeshed
is)
* src.rpms grow a (optional) releases (or whatever) dir.
* under this (optional) dir we have a subdir for each version.
* under that (optional) dir we have a subdir for each release.
* under that (optional) dir we have files for changelogs.
So, the last few ansible builds would have:
ansible-2.9.17-1.fc34:
ansible/releases/2.9.17/1/update-to-2.9.17
ansible/releases/2.9.16/2/conflict-with-ansible-base
ansible/releases/2.9.16/2/Adjust-collections-generator
ansible/releases/2.9.16/1/update-to-2.9.16
...
When building, rpm would sort the releases dir, then the version subdir,
then concat the changelog fragments into a changelog. This way
everything is in the src.rpm.
When doing a PR, you would make a new version subdir and
put a changelog fragment in it and commit it with any of
your other changes.
Probibly some problems with that, but I thought I would throw it out
there from my sleep deprived mind. :)
That still means a particular change needs to "bump" the release number to a
specific value and hence it generates conflicts/mismatch when:
- two or more PRs are opened at the same time
- individual commits are cherry-picked between branches
Hence, not sure if it actually solves some problem.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
