| 1 |
On Fri, 2 Sep 2005, Nick Dimiduk wrote: |
| 2 |
|
| 3 |
> Grobian wrote: |
| 4 |
> > Good point. I have a Panther machine, but I must admit that I do not |
| 5 |
> > test everything on that machine. In that sense it would be nice if |
| 6 |
> > there were ppc-macos-10.3 and ppc-macos-10.4 keywords, as well as |
| 7 |
> > ppc-macos-progressive. |
| 8 |
> |
| 9 |
> I think the cascaded profiles work well for standard vs. progressive |
| 10 |
> installs. It would be quite the fight to get a new keyword for this sort |
| 11 |
> of thing... I'd like to think there's a better solution than a keyword. |
| 12 |
|
| 13 |
I agree, and I'll reiterate my proposal, so that someone can finally shoot |
| 14 |
it down and I can shut up. |
| 15 |
|
| 16 |
I think the progressive profile should be replaced with an upstream darwin |
| 17 |
profile. A macos profile should inherit that and add a prefix. |
| 18 |
|
| 19 |
I don't think a macos keyword is actually needed. If you have a |
| 20 |
ppc-darwin8 keyword, the ppc-macos-10.4 profile could just inherit that |
| 21 |
and add a macos USE flag (for those ebuilds that work differently under |
| 22 |
macos than darwin). |
| 23 |
|
| 24 |
For that to work, you just need more dependency information in the ebuild |
| 25 |
(i.e. if you depend on CoreAudio, or some other part of macos not in |
| 26 |
darwin, it should be listed as a dep). As for how CoreAudio gets into the |
| 27 |
tree, you can keep using package.provided (one version in the profile for |
| 28 |
ppc-macos-10.4 and another in the profile for ppc-macos-10.3) until there |
| 29 |
is a way to detect vendor packages automatically. |
| 30 |
|
| 31 |
Most of this requires the portage rewrite. No idea what you should do |
| 32 |
until then. |
| 33 |
|
| 34 |
-f |
| 35 |
-- |
| 36 |
gentoo-osx@g.o mailing list |
Archives