#283 Break libtaskotron code up into modules so that it can be broken up into subpackages
Closed: Fixed None Opened 8 years ago by tflink.

To solve the large deptree issue, amongst other things, break the libtaskotron code up into modules so we can start splitting functionality up into multiple subpackages. This aims to two concerns at the same time:

  1. With a large deptree, libtaskotron takes a long time to install and pulls in stuff like libvirt and libguestfs on disposable clients when they don't need to be there
  2. We require fedora right now, it'd be nice to open the door to using libtaskotron on centos, debian et. al

This ticket is for pretty much the simplest possible implementation we could do:
* move all the non-core modules into libtaskotron/ext/<module_name>/
* for example, koji_utils.py, bodhi_utils.py, yumrepoinfo.py etc. would go into libtaskotron/ext/fedora
* surround all non-core-functionality imports in directives with try-catch blocks, logging issues if a piece of functionality cannot be imported


This ticket had assigned some Differential requests:
D616

We may want to change the directive doc code up a bit to have a requires: section

Login to comment on this ticket.

Metadata