Just as 2.33 gets into portage, 2.34 comes out ;). An update would be appreciated; it shouldn't be too hard to do. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Look at blender website 2. Emerge -u blender 3. See that you're still stuck with 2.33a Actual Results: I wanted 2.34 to be in portage ;) Expected Results: Installed Blender 2.34
Created attachment 36866 [details] blender 2.34 ebuild here's the ebuild. hope it will enter the portage tree soon
*** Bug 59576 has been marked as a duplicate of this bug. ***
two questions: 1. According to the blender site's info on the Yafray plugin, Yafray 0.0.7 is required to take full advantage of this (Blender directly calling Yafray) 2. Is Yafray an actual dependency of Blender in general or could a USE flag work? I don't see mention of Yafray being actually required except the Yafray 0.0.7 requirement for the plugin to work fully as mentioned in #1 above. Yafray plugin info on the Blender site: http://www.blender3d.org/cms/Yafray_plug-in.377.0.html Previous Blender bug filed that determined version 2.32 does not Depend upon Yafray and is optional. BUG42410 Now about that mozilla plugin :)
2.34 ebuild fails with the following output. scons: *** No Builder for target `blenderplayer', needed by `default'. Stop. scons: building terminated because of errors. !!! ERROR: media-gfx/blender-2.34 failed. !!! Function src_compile, Line 91, Exitcode 2 !!! (no error message)
Same error as comment 4 ...
forced blender-game in the ebuild, that solves the issue... yet another regression from the original ebuild, please cope with that.
the mozilla plugin looks not ready yet. scons is causing me major headache. yafray 0.0.7 on my box produces just black images.
