The attached patch series allows pungi to build 'self-hosting' trees
by resolving all the build dependencies for a package set. It does
not expand the package set for the 'assumed' build depedencies such
as gcc; those are probably better specified in the kickstart file.
As an example, with this, 'pungi --selfhosting' of a kickstart
with just @Core yields over 1200 source packages, and over 500
bin/pungi.py | 7 +++++-
pypungi/__init__.py | 59 +++++++++++++++++++++++++++++++++++++---------------
2 files changed, 48 insertions(+), 18 deletions(-)
Hi. I've written up a proposal for a way to support EPEL builds in
Koji. It's not the only way we could do this, but I think it's doable
with a reasonable amount of effort, and has the side-effect of greatly
simplifying the Koji setup process for a lot of people (by removing the
need to bootstrap/import an entire distro of packages into your private
Koji instance). You can view the proposal here:
It's fairly detailed regarding the data model changes necessary, so if
you're not familiar with the Koji codebase you can skip those parts.
Questions and comments welcome.