Per discussion on bug 499020, adding paths to PYTHONPATH via env.d to support a single consumer is probably not a great idea. It would be nice if you could clean that up.
afais the site-packages dir is accessed in various c++ source files and kind of hardcoded, so moving everything to PYTHON_SITEDIR will need heavy patching using wrappers, I'd have to figure out what kind of binaries get installed for which useflags a lot of work, either way
Ok, this is way getting out of hands. I've just removed the global environment setup completely. Paraviews python shell sets PYTHONPATH automatically so for most use cases everything should work as normal. I've added an elog message for all other use cases. Maybe, we can migrate paraview's python stuff to the system wide site-packages some day... *paraview-4.2.0-r1 (19 Jan 2015) *paraview-4.1.0-r2 (19 Jan 2015) *paraview-4.0.1-r2 (19 Jan 2015) 19 Jan 2015; Matthias Maier <tamiko@gentoo.org> +paraview-4.0.1-r2.ebuild, +paraview-4.1.0-r2.ebuild, +paraview-4.2.0-r1.ebuild, -paraview-4.0.1-r1.ebuild, -paraview-4.1.0-r1.ebuild, -paraview-4.2.0.ebuild: do not set global PYTHONPATH environment variable, bug #499272
