The env vars for crystalspace such as CRYSTAL="/opt/crystal" do not get added The changelog does mention this: crystalspace-20030413-r1 (17 Apr 2003) 17 Apr 2003; Philip Walls <malverian@gentoo.org> crystalspace-20030413-r1.ebuild : Fixed problem with env.d/15crystalspace (vars now on seperate lines) But the 15crystalspace env is missing and does not get added .... Reproducible: Always Steps to Reproduce: 1. 2. 3.
that is correct, the crystalspace no longer generates env.d entries ... all the vars have been moved to the ebuilds themselves ... i guess this aversely affects you ? :)
well appearnly crystalspace is only in the portage for planeshift, even got a cvs version so it'll work with it and no ebuild for the release. and i guess the env vars aren't needed for planetshift. But the env vars are needed for other things ... keanu@jessica crystal $ pwd /opt/crystal keanu@jessica crystal $ ./bin/walktest -video=software Warning: Failed to load `vfs'; use '-verbose' argument for details. Warning: Failed to load `vfs'; use '-verbose' argument for details. WARNING: could not load plugin 'crystalspace.kernel.vfs' Couldn't load vfs plugin! Failed to initialize config! Error initializing system! Cleaning up... keanu@jessica crystal $ export CRYSTAL="/opt/crystal" keanu@jessica crystal $ ./bin/walktest -video=software Using alternative 3D driver: crystalspace.graphics3d.software tri:116 vt:66 Load TYPE plugin crystalspace.mesh.object.emit Total level load time: 0.938 seconds
ok, fixed in cvs, sorry for the trouble
*** Bug 27165 has been marked as a duplicate of this bug. ***
