Requires: PYTHON_SINGLE_TARGET="python2_7 -python3_4" emerge =www-apache/mod_wsgi-4.5.7 www-apache/mod_wsgi-4.5.7::gentoo PYTHON_SINGLE_TARGET="python2_7 -python3_4" PYTHON_TARGETS="python2_7 python3_4" net-analyzer/graphite-web-0.9.13-r3::gentoo USE="carbon mysql sqlite -ldap -memcached -postgres" PYTHON_TARGETS="python2_7" For graphite-web to work. If not you will end up with graphite module not found.
I'm not sure what is the actual problem here. You can apparently use graphite-web just fine without using www-servers/apache. If you happen to want both, then your local configuration dictates that mod_wsgi should be configured for graphite-web. On the other hand, that requirement in your local configuration should not dictate an automatic dependency in the ebuild, which would inconvenience people who want graphite-web but not apache.
I am reinstalling this on a new system. Hence the revisit of this old bug. The apache dependencies does require this mod_wsgi. Maybe add a USE flag for apache ?
how about an einfo that mod_wsgi is necessary for use with apache?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f9f3a84fbb4222f389779e9f434a5c2a2712eb0c commit f9f3a84fbb4222f389779e9f434a5c2a2712eb0c Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2018-08-16 10:13:17 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2018-08-16 10:13:17 +0000 net-analyzer/graphite-web: add stronger hint about wsgi install Closes: https://bugs.gentoo.org/618030 Package-Manager: Portage-2.3.40, Repoman-2.3.9 net-analyzer/graphite-web/graphite-web-1.1.3-r1.ebuild | 2 ++ 1 file changed, 2 insertions(+)
This is a fine solution
