On 5/14/19 7:58 AM, Tomas Kopecek wrote:
Maybe it would be useful to create some meta-subpackages, ala
koji-builder-imagefactory, koji-builder-yum, which will encapsulate
those optional dependencies? Would it be more transparent?
I really like this idea. Koji is a valuable tool, but the learning
curve is steep if you come to set it up for personal/biz use with no
prior experience (and is doubly compounded if your X.509 or Kerberos
knowledge is weak). I believe such a split would greatly simplify the
initial installation if coupled with some docs that explained, "You'll
always need a Hub, DB and one or more Builders. Depending on what kind
of tasks you want Koji to do, you may also want ..." Of course, it
would need a bit more detail about what packages that entails.
I'd be happy to help with such an effort.