Tom Gundersen
Tom Gundersen
Hmm, with depsolving in the workers, do we need this at all?
This is nonzero on azure by default. cc @gicmo @thozza
At the moment the koji API does not support customisations, which is why it just uses the standard blueprints. It only builds "plain" images. This is something we could in...
Note that we can only do this once we are appropriately security hardened. And we should extend composer to take the extra repos only for the image content, not from...
I'm unlikely to have time to finish this up, feel free to take it over / consider it an RFE, if anyone is interested.
(or close it :) )
Over all I agree with your proposals. We may need to consider if we need to support minor versions when we make additions to our API, if this is something...
So `v1.1` should be backwards compatible with `v1.0`, so worst case a client expecting `v1.0` and getting `v1.1` will get some additional stuff they can ignore... Not sure if that...
One thing to keep in mind: ideally we would push the searching down to dnf eventually, rather than do it ourselves. So let's check that dnf supports whatever features we...
Perfect! Thanks for checking :)