Allow the usage of jinja2 templates

This drops the hard requirement on Cheetah.

Jinja is a python 2.4->3.x compatible templating engine, allow its
optional usage (until we can depreciate cheetah) by allowing for
specifying a template file header that can define which template engine to
use.

If the template file header does not specify a renderer, then assume
that that is cheetah.  If cheetah is not available, then use a limited
builtin renderer on a best effort basis, and log the warning.

LP: #1219223

1 files changed, 1 insertions, 0 deletions

diff --git a/packages/brpm b/packages/brpm
index f8ba1db1..b8bbff9d 100755
--- a/packages/brpm
+++ b/packages/brpm
@@ -37,6 +37,7 @@ PKG_MP = {
     'redhat': {
         'argparse': 'python-argparse',
         'cheetah': 'python-cheetah',
+        'jinja2': 'python-jinja2',
         'configobj': 'python-configobj',
         'jsonpatch': 'python-jsonpatch',
         'oauth': 'python-oauth',