I just saw the Koji 2.0 presentation online, and I'm quite interested in
it, especially with the concept of being able to build more than RPMs. For
example, I'd like to see Koji to be able to do reproducible builds of
Debian packages with debbuild (using RPM spec to build Debian packages)
or even traditional methods, virtual machine bundles (qcow2 and ova),
container bundles (Nulecule, appc), and some configurability to support
building for a multitude of distros and targets.
Essentially, I'd like to see some of the interesting capabilities that the
Open Build Service (building for multiple distribution targets, building
virtual machines, container bundles) in a nice, easy to deploy Python
3.x-compatible application. OBS is difficult to set up, maintain, and
integrate into existing workflows, while Koji doesn't try to be an
all-in-one replacement for everything.
Would Koji 2.0 be flexible enough to do all these things without becoming
like the OBS?
Also, on another note, why can't Koji 2.0 use the Python 3.4 Software
Collections on RHEL 6/7? RHEL 7 now has Python 3.4 in EPEL, too.
真実はいつも一つ！/ Always, there's only one truth!