From: m h <sesquile@gmail.com>
To: gentoo-osx@lists.gentoo.org,
Michael Haubenwallner <michael.haubenwallner@salomon.at>
Subject: Re: [gentoo-osx] PREFIX the next generation...
Date: Mon, 19 Dec 2005 14:49:15 -0800 [thread overview]
Message-ID: <e36b84ee0512191449qee7d18tff4f88f99e6e4823@mail.gmail.com> (raw)
In-Reply-To: <20051219212509.GZ29216@gentoo.org>
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 <grobian@gentoo.org> 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...
>
>
--
gentoo-osx@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-19 22:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 21:07 [gentoo-osx] PREFIX the next generation m h
2005-12-19 21:21 ` [gentoo-osx] " m h
2005-12-19 21:26 ` m h
2005-12-19 21:30 ` Grobian
2005-12-19 21:25 ` [gentoo-osx] " Grobian
2005-12-19 22:49 ` m h [this message]
2005-12-19 23:20 ` Kito
2005-12-20 1:33 ` m h
2005-12-20 6:32 ` Grobian
2005-12-20 9:23 ` Grobian
2005-12-20 20:11 ` m h
2005-12-20 20:53 ` Grobian
2005-12-20 23:00 ` m h
2005-12-20 23:20 ` m h
2005-12-21 0:09 ` m h
2005-12-21 12:50 ` Grobian
2005-12-22 6:57 ` Brian Harring
2005-12-22 7:02 ` Brian Harring
2005-12-22 10:35 ` Grobian
2005-12-21 13:26 ` Grobian
2005-12-20 22:18 ` Kito
2005-12-20 22:22 ` Kito
2005-12-21 9:39 ` Michael Haubenwallner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e36b84ee0512191449qee7d18tff4f88f99e6e4823@mail.gmail.com \
--to=sesquile@gmail.com \
--cc=gentoo-osx@lists.gentoo.org \
--cc=michael.haubenwallner@salomon.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox