I think it would be useful to be able to submit multiple packages with dependencies between them, without waiting for the BS to finish the first package to submit the 2nd one. For this, I think there is different ways we can do it : - add option in submit to give other jobs IDs as dependencies. However if first build fail, the other will fail too and have to be submitted again. - add option in submit to give packages with version and release as dependencies. - add version and release for BuildRequires inside the spec file. And the package stays in the todo queue until all BuildRequires are available. Reproducible: Steps to Reproduce:
If we decide to go the 3rd way, this will mean that we need a way for a user to remove a build ( or, if he does a typo as this could prevent a job from completing ). What is the use case of the feature ?
CC: (none) => misc
Yes, a way to cancel builds will become mandatory if we do this. Even if we don't do this, a way to cancel build would be useful I think, as there is sometime requests from people who want to cancel builds they submitted by error. Use case for build dependencies would be for instance with many packages with build dependencies between them, that need to be rebuilt in the right order. Currently you need to submit the first package, wait for the build to finish, submit the 2nd package, wait for the build to finish, submit the 3rd, etc ... If we do this, you can update the versions in the BuildRequires in all spec files, and submit everything in any order. I have heard at Mandriva previously, from people packaging KDE or E17 that something like this would be useful.
Then another potential idea would be to push such scripting ( because that sound like it ) on client side, and let people write script to submit more than one package, or trigger built based on BS results. I would see a use case if we could add --define on build. Latest python upgrade was quite hellish due to lack of botstrap option. But if we could say "rebuild everything using --define bootstrap and then rebuild them without it", this would be helpful : - no more information stored only in my head ( with all potential bus error problem ) - no more work to check everything is done before pushing the rest of the upgrade Downside would be to either write a DSL for that, or to discuss ad-vitam eternam on which language to use, and later with communication system to use :) ( also on canceling build : https://bugs.mageia.org/show_bug.cgi?id=635, I just fill a bug request ).
Blocks: (none) => 858
any updates on this issue?
CC: (none) => marja11
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED. Please set status to ASSIGNED. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
Status: NEW => ASSIGNED
What about of make a BS based on fedora's copr? it already have this kind of feature, you can star the pkg1 build , copy the number of work and for the pkg2 that depends of pkg1 specify to wait until number of work for pkg1 ends