On Fri, Jan 27, 2006 at 07:52:44PM +0100, Grobian wrote:
> On 27-01-2006 09:12:43 -0800, Brian Harring wrote:
> > > Nope, it's related to the later portage tools dropping 'hardcoded
> > > support' for OSX, that's why I haven't keyworded the newer version,
> > > because it simply generates python stack traces for some tools (not
> > > emerge), which I don't consider to be "good".  It was deliberately not
> > > fixed (sort of impossible), hence deliberately not keyworded by me.
> > 
> > What tools?
> > Granted, buttload of portage bugs (thus easy to miss something), but 
> > portage bundled tools should be forcing sys.path mangling.
> 
> Bug #113551
> 
> Problem is IMHO that on our current setup our shells don't get the stuff
> from portage, because the shells don't come with the gentoo rc scripts.

Err... legacy crap (yay).
Comment regarding "won't be a problem for long"- would be nice having 
some clarification on that one :)

The tools that are broken *still* should be external to portage 
(exception is emaint).  Any others, should have the hardcoded 
insertion.
~harring

Attachment: pgpoMNXHcppih.pgp
Description: PGP signature

Reply via email to