Greetings.
A group of folks are looking at getting modular content in the non
modular buildroot in fedora. 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) and then adding them
as a external repo the buildroot inherits.
The question has come up how we want to regenerate this repo, and I
wondered if perhaps we could expand kojira to do it? Is that too much
scope creep for kojira? I know the above plan has external repos, but
what if we didn't do external and could 'teah' kojira how to detect when
this modular buildroot repo was out of date and fire off a pungi compose
to update it? basically making kojira more generic and handling rpm
buildroots and regenerating them as a single case.
Is this something that sounds workable? Or should we look at doing
something completely external to koji here?
kevin
_______________________________________________
koji-devel mailing list -- koji-devel@lists.fedorahosted.org
To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.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.fedorahosted.org/archives/list/koji-devel@lists.fedorahosted.org