Kito wrote:
Would you like to lead this sub-project, define roles, tasks and roll
out a todo list or some minimalistic readme, so people can get
involved and perhaps start wondering around in the code?
I'm not sure it warrants a sub-project, but if the consensus is that it
does, I suppose I could lead it if noone else wants to. Hopefully I'll
have some stuff to post in the coming week - an xml project page, very
very rough 'getting started' doc, a prefixed os x stage1/3, pkg
installer, and overlay snapshot. Considering the fragile nature of it
all, and that whatever we/I come up with will function merely as a
working prototype, I'm not sure how 'official' it should really get...
sub-project is as large as you want it to be. I didn't want to write
'project' because I don't want to refer to the Gentoo for OSX project as
a whole. This thing of portage with prefixes, that's what I meant and
it's yours.
Because I still don't understand the idea of progressive, and I do
understand myself a bit sometimes. So for me, progressive is a skim
that exists in bugzilla, but every bug assigned to progressive is
basically dead. ~ppc-macos is simply the testing side of the mainline
product we have.
But again, without the progressive profile, this past weekend when it
came time to get all the system packages merging, I would have been
starting from square1, as opposed to being able to quickly take
advantage of ~12 months of hard work. Had we/I not had this means of
keywording packages that collide with apple files, I'd still be fighting
with spanky on getting the bash ebuild darwin-safe, instead of tackling
the global problems of getting prefixes working.
Yes, but then I come in again from my management perspective, and I say:
"Progressive as in user product doesn't work!".
But really. The work you describe is pure development efforts (luckily)
spent before you could actually use it. It takes insight and
recognition to do something like that. Kudos to you to identify the
need upfront!
I would personally 'hide' it away behind a development thing, not cover
it under "this is for the real die hards that want bleeding edge stuff:
progressive". Because in the latter it isn't clear why you're doing it,
and some users might think it's simply *cool*. No, it should be a clear
development thing with development hazards, absolutely not meant for any
user, unless those that want to sacrifice and contribute their 'blood'.
Well, ok, that's my thinking.
The only way out of there is what ciarmn would like to see
the best: remove the full ppc-macos keyword from the tree. Then what
ciarmn wouldn't like so much to see is that you can start all over
from scratch in an overlay.
I'm not sure I followed that thought.
It's IMHO just not an option. At least I won't allow you to do it. :)
Anyway, it's good to know that we're basically on the same route.
--
Fabian Groffen
Gentoo for Mac OS X Project -- Interim Lead
--
[email protected] mailing list
