Bug 210258

Summary:	ebuild helper functions should use absolute paths if possible
Product:	Portage Development	Reporter:	Alex <Alex>
Component:	Core - Ebuild Support	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	minor
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Alex 2008-02-15 17:11:26 UTC

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

Comment 1 SpanKY gentoo-dev

2008-02-15 19:04:28 UTC

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

Comment 2 Jakub Moc (RETIRED) gentoo-dev

2008-02-17 20:27:19 UTC

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?