Jinja 2.1 was released a couple of days ago, which brings much-needed features. I would (really) like to see this in the tree, so i tried a simple ebuild bump which unfortunately didn't work. Since epatch uses ${P} - the path to "nodoc"-patch will err. I chose to statically enter versioning info in the 2.1 ebuild (diff to 2.0 ebuild is attached) so one doesn't have to bump the 2.0 ebuild as well. While we're at it, why is jinja2 a separate package from jinja? Backwards compability isn't far from other applications "major" version bumps (I for one made very minor changes in 10 of my ~100 templates). Thanks! Reproducible: Always Steps to Reproduce:
Created attachment 173308 [details, diff] Diff that turns jinja2-2.0 into jinja2-2.1
+ 06 Dec 2008; Patrick Lauer <patrick@gentoo.org> +jinja2-2.1.ebuild: + Bumping to 2.1, closing #248752
