On 01 Jun 2015 11:49, Zac Medico wrote:
> On 06/01/2015 10:25 AM, Mike Frysinger wrote:
> > (a) just throw an error and exit when PORTAGE_BIN_PATH is not set ... 
> > considering the current portage code points to a path where it is no longer 
> > installed, maybe that's ok ?  the recent changes to make portage install 
> > copies
> > for each python version is what broke it i think.
> 
> I like this idea. I can't think of a reason why we should allow
> PORTAGE_BIN_PATH to be unset.

i'll try this in the CrOS project where we're using Gentoo/Prefix and see how 
it 
goes.  and then try it on my system for a while to further check it.  otherwise
i'll go with Tim's inspired idea about symlinked wrappers.
-mike

Attachment: signature.asc
Description: Digital signature

Reply via email to