From: Brian Harring <ferringb@gentoo.org>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] The road ahead?
Date: Tue, 1 Nov 2005 20:33:07 -0600 [thread overview]
Message-ID: <20051102023307.GC16594@nightcrawler> (raw)
In-Reply-To: <65C7CF99-1E15-49EE-85F2-E08AC12CD177@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Tue, Nov 01, 2005 at 02:10:03PM -0600, Kito wrote:
> I'll let Brian answer this, but I'm fairly certain there is no chance
> of this making it into the 2.0 series, 2.1 is dead, so 3.0 will have
> to be our saviour (boooo! hsssss! bad pun)
No way in hell on 2.0; 2.1 was released dead (the major changes of it
are a year old), 3.0 would be the only _potential_ portage target.
Why did I say potential?
Cause I'm after making an ancillary point so everyone is on the same
page here- portage will *not* have any prefix support without the
ebuild changes being vetted by gentoo community.
What's being worked on is a prototype- the prototype will be useful on
it's own, but the main point of it is demonstrating that it's doable
and the pros/cons of it.
Please keep this in mind. Bit of a reality check (kito and I are
operating under this)- comments of the sort "when portage supports
prefix "...
Portage will only mainline support PREFIX if devs agree to the underlying
ebuild changes. So... help make it clean, but be aware of the rules being
operated under please.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-02 1:33 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 10:49 [gentoo-osx] The road ahead? Grobian
2005-10-30 17:15 ` Stroller
2005-10-31 5:25 ` Lina Pezzella
2005-10-31 18:58 ` Grobian
2005-10-31 18:52 ` Kito
2005-10-31 19:34 ` Grobian
2005-10-31 21:42 ` Kito
2005-10-31 22:20 ` Grobian
2005-11-01 22:45 ` Lina Pezzella
2005-11-02 0:06 ` Kito
2005-11-02 7:29 ` Grobian
2005-11-01 0:16 ` m h
2005-11-01 0:32 ` Brian Harring
2005-11-01 0:59 ` Kito
2005-11-01 19:16 ` m h
2005-11-01 20:10 ` Kito
2005-11-01 20:16 ` Nathan
2005-11-01 20:21 ` Grobian
2005-11-01 20:37 ` Kito
2005-11-01 20:45 ` Grobian
2005-11-01 20:58 ` Kito
2005-11-01 21:05 ` Grobian
2005-11-01 22:01 ` m h
2005-11-01 22:55 ` Kito
2005-11-04 17:50 ` m h
2005-11-08 1:48 ` m h
2005-11-08 16:53 ` Grobian
2005-11-08 17:09 ` Kito
2005-11-08 21:10 ` m h
2005-12-05 5:19 ` m h
2005-12-05 17:20 ` Kito
2005-11-02 2:33 ` Brian Harring [this message]
2005-11-02 3:00 ` Kito
2005-11-02 4:12 ` Brian Harring
2005-11-02 4:16 ` Nathan
2005-11-02 5:52 ` Brian Harring
2005-11-01 1:20 ` m h
2005-11-01 1:57 ` Brian Harring
2005-11-01 0:51 ` Kito
-- strict thread matches above, loose matches on Subject: below --
2005-10-31 22:17 dirk.schoenberger
2005-10-31 23:12 ` Kito
2005-10-31 23:49 ` dirk.schoenberger
2005-11-01 7:33 ` Grobian
2005-11-01 16:07 ` Nathan
2005-11-01 16:28 ` Kito
2005-11-01 16:55 ` Nathan
2005-11-01 17:17 ` Grobian
2005-11-01 18:09 ` Nathan
2005-11-01 19:03 ` m h
2005-11-01 19:13 ` Grobian
2005-11-01 19:32 ` m h
2005-11-01 19:36 ` Grobian
2005-11-01 19:45 ` m h
2005-11-01 19:14 ` Nathan
2005-11-01 16:57 ` dirk.schoenberger
2005-11-01 17:26 ` Grobian
2005-11-01 18:08 ` Nathan
2005-11-01 19:35 dirk.schoenberger
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=20051102023307.GC16594@nightcrawler \
--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