Writing my own ebuild I came across the problem that newinitd was using a script called 'install' to insert the init script into etc/init.d However I am required to overwrite the PATH env variable in my src_install() so there was another install script in the path which newinitd used instead - and of course failed. If possible I would propose the ebuild helper functions such as newinitd use absolute paths instead. Reproducible: Always Steps to Reproduce: 1. overwrite PATH environment variable with a path whit an executable named install 2. run newinitd 3. newinitd will run your install instead of the portage one Expected Results: newinitd (and possibly others as well) should use absolute paths You can easily work around that by saving the old PATH and setting it again before calling newinitd
your ebuild is incorrect then ... override PATH on a per-program invocation, or dont muck with it at all `install` is a core binary that many things rely upon
As said above. Also killing portage functions when something in coreutils etc. changes path (which happened quite a lot recently) just because someone wrote a broken ebuild rocks... @ portage folks - could we please start killing this and similar bugs ASAP so that they stop messing with search for actually useful issues?
