Is it possible to teach Koji to build packages for the same architectures twice, with slightly different buildroots? The buildroots would have different %dist macro definitions, and as a result the binary packages would have distinct NEVRAs.
Thanks, Florian
Alll you would need to do is have a different target. Or are you talking one koji call, and it builds on both targets automatically?
On Thu, Nov 14, 2019 at 4:17 AM Florian Weimer fweimer@redhat.com wrote:
Is it possible to teach Koji to build packages for the same architectures twice, with slightly different buildroots? The buildroots would have different %dist macro definitions, and as a result the binary packages would have distinct NEVRAs.
Thanks, Florian _______________________________________________ buildsys mailing list -- buildsys@lists.fedoraproject.org To unsubscribe send an email to buildsys-leave@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/buildsys@lists.fedoraproject.o...
* Troy Dawson:
Alll you would need to do is have a different target.
Well, that would sort-of imply using koji-shadow (or what it was called) if these builds are supposed to happen in parallel to official builds. And I don't think we want koji-shadow for Fedora.
Or are you talking one koji call, and it builds on both targets automatically?
The latter.
Thanks, Florian
On Thu, Nov 14, 2019 at 5:17 AM Florian Weimer fweimer@redhat.com wrote:
Is it possible to teach Koji to build packages for the same architectures twice, with slightly different buildroots? The buildroots would have different %dist macro definitions, and as a result the binary packages would have distinct NEVRAs.
You'd need to write some client tooling to submit two different "build" RPCs to the hub. If you want to do it server-side, an alternative would be to write a Koji hub plugin that either hooks into Koji's main "build" method, or implements an entirely new RPC like "buildMulti" or something and accepts a list of build target names.
If you're just experimenting, it would be a good idea to start with a client-side implementation.
- Ken
On Thu, Nov 14, 2019 at 01:17:40PM +0100, Florian Weimer wrote:
Is it possible to teach Koji to build packages for the same architectures twice, with slightly different buildroots? The buildroots would have different %dist macro definitions, and as a result the binary packages would have distinct NEVRAs.
Couldn't this be done with package.cfg targets, as with epel8 and epel8-playground?
* Matthew Miller:
On Thu, Nov 14, 2019 at 01:17:40PM +0100, Florian Weimer wrote:
Is it possible to teach Koji to build packages for the same architectures twice, with slightly different buildroots? The buildroots would have different %dist macro definitions, and as a result the binary packages would have distinct NEVRAs.
Couldn't this be done with package.cfg targets, as with epel8 and epel8-playground?
Do you have any documentation for that? The only reference to package.cfg I could find in the Fedora wiki is something hidden (literally) in the Package maintenance guide, but it refers to modules.
Ideally, I want to rebuild the entire distribution with a slightly different buildroot, and this seems to require editing all packages, so that's not a good solution for me.
Thanks, Florian
buildsys@lists.fedoraproject.org
-
Florian Weimer -
Ken Dreyer -
Matthew Miller -
Troy Dawson