The ebuild for blender creates /etc/env.d/60blender with the following contents:
The primary problem with this is that when Blender is newly installed, it will not start correctly without the user logging in again or sourcing /etc/profile. It pollutes the environment of all programs with meaningless information. The installation paths should be hardcoded into the executable, as for almost every other program.
Steps to Reproduce:
1. Make sure you don't have Blender installed, no /etc/env.d/60blender and your environment doesn't have any BLENDER_* variables.
2. Install Blender.
3. Start it.
It prints lots of error messages and shows up with lots of missing things.
The current ebuild produces the following message concerning this problem, but it only mentions upgrades and not new installs:
*** If you're updating from blender before 2.63a, please make
*** sure to log out and then back in before launching it, so
*** that the new environment variables are picked up.
21 Jul 2012; Diego E. Pettenò <email@example.com> blender-2.63a-r2.ebuild:
Add a warning about the need for logging out and back in.
I suspect that it might not even be needed anymore for media-gfx/blender-2.66 although I did not remove the env.d file
+*blender-2.67b-r1 (21 Jun 2013)
+*blender-2.66-r1 (21 Jun 2013)
+ 21 Jun 2013; Julian Ospald <firstname.lastname@example.org> -blender-2.66.ebuild,
+ +blender-2.66-r1.ebuild, +files/blender-2.66-sse2.patch,
+ -blender-2.67b.ebuild, +blender-2.67b-r1.ebuild,
+ fix dependencies wrt #466020, improve sse2 handling wrt #469134, remove env.d
+ file wrt #447626, fix fftw useflag, update REQUIRED_USE, allow running
+ src_install multiple times