| 1 |
On Fri, Jan 27, 2006 at 07:52:44PM +0100, Grobian wrote: |
| 2 |
> On 27-01-2006 09:12:43 -0800, Brian Harring wrote: |
| 3 |
> > > Nope, it's related to the later portage tools dropping 'hardcoded |
| 4 |
> > > support' for OSX, that's why I haven't keyworded the newer version, |
| 5 |
> > > because it simply generates python stack traces for some tools (not |
| 6 |
> > > emerge), which I don't consider to be "good". It was deliberately not |
| 7 |
> > > fixed (sort of impossible), hence deliberately not keyworded by me. |
| 8 |
> > |
| 9 |
> > What tools? |
| 10 |
> > Granted, buttload of portage bugs (thus easy to miss something), but |
| 11 |
> > portage bundled tools should be forcing sys.path mangling. |
| 12 |
> |
| 13 |
> Bug #113551 |
| 14 |
> |
| 15 |
> Problem is IMHO that on our current setup our shells don't get the stuff |
| 16 |
> from portage, because the shells don't come with the gentoo rc scripts. |
| 17 |
|
| 18 |
Err... legacy crap (yay). |
| 19 |
Comment regarding "won't be a problem for long"- would be nice having |
| 20 |
some clarification on that one :) |
| 21 |
|
| 22 |
The tools that are broken *still* should be external to portage |
| 23 |
(exception is emaint). Any others, should have the hardcoded |
| 24 |
insertion. |
| 25 |
~harring |
Archives