From: Brian Harring <ferringb@gentoo.org>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Current installation method
Date: Fri, 27 Jan 2006 20:08:37 -0800 [thread overview]
Message-ID: <20060128040836.GH17550@nightcrawler.had1.or.comcast.net> (raw)
In-Reply-To: <20060127195058.GB10049@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
On Fri, Jan 27, 2006 at 08:50:58PM +0100, Grobian wrote:
> On 27-01-2006 11:16:05 -0800, Brian Harring wrote:
> > > 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 :)
>
> Problem does not occur to me in prefixed portage. "long" is a relative
> thing. :p
>
> > The tools that are broken *still* should be external to portage
> > (exception is emaint). Any others, should have the hardcoded
> > insertion.
>
> Ehm, ok. When will your 'fix' be available for us? In next snapshot
> release of portage 2.1? Thanks by the way.
At least for emaint, commited the path insertion earlier today.
You're going to need to be a bit more specific if there are others
failing though.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-28 4:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 23:08 [gentoo-osx] Current installation method Nick Dimiduk
2006-01-26 8:22 ` Grobian
2006-01-26 17:28 ` Nick Dimiduk
2006-01-26 18:21 ` Grobian
2006-01-27 3:39 ` Kito
2006-01-27 3:33 ` Kito
2006-01-27 9:14 ` Grobian
2006-01-27 17:12 ` Brian Harring
2006-01-27 18:52 ` Grobian
2006-01-27 19:16 ` Brian Harring
2006-01-27 19:50 ` Grobian
2006-01-28 4:08 ` Brian Harring [this message]
2006-02-03 2:22 ` Marcin Gabrowski
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=20060128040836.GH17550@nightcrawler.had1.or.comcast.net \
--to=ferringb@gentoo.org \
--cc=gentoo-osx@lists.gentoo.org \
/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