On Fri, Sep 20, 2019 at 09:32:09AM +0200, Miroslav Suchý wrote:
Can we instead of:
> The current plan for this has us creating a
> list of modules (starting with the default modules and adding a few)
> that we want to be in the buildroot, doing a pungi compose to gather
> them into a repo (all marked default in that repo)
teach Koji(ra) to consume modules as modules and put into Mock config:
config_opts['module_enable'] = ['list', 'of',
config_opts['module_install'] = ['module1/profile',
Well, the problem there is that we need a place to download and install
and enable the modules from (in the buildroot). We could add the
fedora-modular repo as a extenal repo, but then we loose some
reproducability, and we can't update it as much (so mbs builds needing a
chain would fail or wait for a day).
We could have a script that adds modules we wants tags into the
buildroot, but thats basically ursa major that we don't want to use.
I have to admit that I do not know what is responsible to create
module artifact (rpm repo with modulemd metadata). Is it Pungi or MBS?
Well, MBS builds everything and creates a repo with the finished module,
pungi gathers up all the modules from their tags and makes a
fedora-modular repo from it that is the thing that is pushed out.