| 1 |
I'm basically at the same state with Haubi's toolsbox and your method. |
| 2 |
After chatting with Kito I'm also thinking about sticking with |
| 3 |
toolsbox. (Since it is pretty generic and should run on most any |
| 4 |
unix). Kito also helped explain the next steps with seem to be coming |
| 5 |
up with virtuals/package.provided for (taken from emerge info): |
| 6 |
dev-lang/python: [Not Present] |
| 7 |
sys-apps/sandbox: [Not Present] |
| 8 |
sys-devel/autoconf: [Not Present] |
| 9 |
sys-devel/automake: [Not Present] |
| 10 |
sys-devel/binutils: [Not Present] |
| 11 |
sys-devel/libtool: [Not Present] |
| 12 |
sys-devel/odcctools: [Not Present] |
| 13 |
virtual/os-headers: [Not Present] |
| 14 |
|
| 15 |
Haubi- How did you deal with this in your 2.1 tree? |
| 16 |
Also why is emerge -av system trying to installing portage2.1? |
| 17 |
|
| 18 |
|
| 19 |
On 12/19/05, Grobian <grobian@g.o> wrote: |
| 20 |
> Just to give you an update. I ended more or less in the same state as |
| 21 |
> you. Though I think I know why it's so stubborn. Portage seems to |
| 22 |
> expect all binaries and stuff in the prefixed location. I added |
| 23 |
> (symlinked) /bin/bash in my prefix, and was after that able to run |
| 24 |
> ebuild xxxx digest for instance. |
| 25 |
> |
| 26 |
> So my thoughts were actually to give haubi's box a fling again, because |
| 27 |
> it might install the minimal set of tools necessary. Sigh. I need |
| 28 |
> longer weekends and much more hair to pull ;) |
| 29 |
> |
| 30 |
> Not going into IRC now, because I try to stay away from it at least |
| 31 |
> during the week, to be able to actually do something... |
| 32 |
> |
| 33 |
> |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-osx@g.o mailing list |
Archives