Le 2020-07-08 17:19, Pavel Raiskup a écrit :
Small experiment (few-liner) for copr with "%bid, build system tag":
https://pagure.io/copr/copr/pull-request/1436
Well, that ties the system to corp, not koji, and like the other
proposal, that makes releases that do not import from one system to
another (which definitely matters to me, because my packager workflow
has rpmbuild, mock, copr and koji stages).
I honestly do not see how you can bump safely, without providing the
bumping code the "bump from that point" information.
When you bump, you graft new release growth over an existing release
tree. Stacking something blindly without looking upon where you stack it
will work in a lot of cases, but will fail horribly in others. I like
KISS but this KISS is too SS for my tastes. If linear history worked for
a project the size of Fedora we’d be all still using CVS.
The bumping code itself is not hard to write
Serializing 'bump from here' in a format that can be reliably read later
is also not hard (as long as you do not insist on expanding Release and
trying to decompose it back at the next build).
The hard part is moving 'bump from here' info between builds.
Regards,
--
Nicolas Mailhot
_______________________________________________
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
