I'm basically at the same state with Haubi's toolsbox and your method. After chatting with Kito I'm also thinking about sticking with toolsbox. (Since it is pretty generic and should run on most any unix). Kito also helped explain the next steps with seem to be coming up with virtuals/package.provided for (taken from emerge info): dev-lang/python: [Not Present] sys-apps/sandbox: [Not Present] sys-devel/autoconf: [Not Present] sys-devel/automake: [Not Present] sys-devel/binutils: [Not Present] sys-devel/libtool: [Not Present] sys-devel/odcctools: [Not Present] virtual/os-headers: [Not Present]
Haubi- How did you deal with this in your 2.1 tree? Also why is emerge -av system trying to installing portage2.1? On 12/19/05, Grobian <[EMAIL PROTECTED]> wrote: > Just to give you an update. I ended more or less in the same state as > you. Though I think I know why it's so stubborn. Portage seems to > expect all binaries and stuff in the prefixed location. I added > (symlinked) /bin/bash in my prefix, and was after that able to run > ebuild xxxx digest for instance. > > So my thoughts were actually to give haubi's box a fling again, because > it might install the minimal set of tools necessary. Sigh. I need > longer weekends and much more hair to pull ;) > > Not going into IRC now, because I try to stay away from it at least > during the week, to be able to actually do something... > > -- [email protected] mailing list
