I have freewrl working just fine from portage...please keyword ~amd64 when you get a chance...
Tested media-gfx/freewrl-1.16.1 USE="nsplugin -minimal" for ~amd64. ------------------------------ NB ------------------------------ I'm currently getting a collision with FEATURES="collision-protect": existing file /usr/lib64/perl5/5.8.8/x86_64-linux/perllocal.pod is not owned by this package This needs to be resolved before this package can be marked stable. ------------------------------- With collision-protect disabled, the package builds and installs. Tested against the vrml samples at http://ovrt.nist.gov/projects/vrml/vrmlfiles.html eg: freewrl ttp://www.nist.gov/itl/div894/ovrt/projects/vrml/urlHouseCol.wrl The application launches, but I get repetetive "Could not find System Fonts for Text nodes" errors thrown to console. After a long wait, I ctrl-c out. Nothing gets rendered to browser. Might be something mal-configured on my system, but for now, declining to recommend for ~amd64.
This is a problem with the package installing the fonts in /usr/lib64/perl5/<version>/VRML instead of /usr/lib64/perl5/<version>/VRML/fonts which is where it is looking for them at. It would make better sense to make this package depend on media-fonts/ttf-bitstream-vera and media-fonts/font-bitstream-type1, and use the system font path instead.
(In reply to comment #2) > This is a problem with the package installing the fonts in > /usr/lib64/perl5/<version>/VRML instead of > /usr/lib64/perl5/<version>/VRML/fonts which is where it is looking for them at. > > It would make better sense to make this package depend on > media-fonts/ttf-bitstream-vera and media-fonts/font-bitstream-type1, and use > the system font path instead. > reassinging bug
have the fonts not found problem too.
Hope this is now fixed, I now symlink ttf-bitstream-vera-fonts-package. You'll have to remove all old freewrl-versions before merging though because else the symlink-setting will boil out.
done
