Emerging app-misc/when fails when FEATURES=test, because the tool requires a semi-setup work environment and attempts to call the binary without a path from the Makefile. The attached patch fixes both these problems, and allows the building of when if FEATURES=test is set. Thanks James
Created attachment 90391 [details, diff] when-fix_test_environment.patch
we can't touch ${HOME} from an ebuild, it violates our sandbox environment. i've added a test restriction to the ebuild instead.
First, thanks for getting around to this bug. > ------- Comment #2 from dirtyepic@gentoo.org 2007-01-19 04:49 -0800 ------- > we can't touch ${HOME} from an ebuild, it violates our sandbox environment. > i've added a test restriction to the ebuild instead. Please reconsider this change. Using HOME isn't a sandbox violation, because it doesn't touch any files outside of portage's temp directory. Portage creates a package specific HOME for use by ebuilds. Take a look at /usr/lib/portage/pym/portage.py to see the implementation or just add an 'echo $HOME' to an ebuild to see it in action ;) Paludis also handles this in ebuild/builtin_init.bash and pkgcore in pkgcore/ebuild/ebd.py, admittedly I haven't tried either of those just read the source. Thanks, James
well, learn something new every day. ;) i've undone my change and applied your patch. thanks.
