On Tue, Jun 10, 2014 at 5:30 PM, Jamie Strandboge <jamie@xxxxxxxxxxxxx> wrote:
An idea I had was to make click-reviewers-tools entirely self-contained. Ie, it
ships the policy files in its own click-reviewers-tools directory along with all
the frameworks it wants to support. This does add a maintenance burden, but I
don't think too much. We could automate slurping in the bits we embed in the
package. This has a lot of benefits:
* it works easily with the SDK (they don't need a separate chroot)
* we don't have to install different frameworks on the machine doing the
reviewing
* we don't have to install new apparmor policy and/or apparmor on the machine
doing the reviewing
* SRUs or -backports are pretty simple
* the automated reviews machine can stay on an LTS
Big +1 from me.
