| 1 |
I'm not interested at all in this bug in specific, I'm interested in the |
| 2 |
visions on using ~ppc-macos vs ppc-macos. |
| 3 |
|
| 4 |
If you keyword ~ppc-macos should you be on a completely ~ppc-macos |
| 5 |
system, or does a ppc-macos system also hold? |
| 6 |
|
| 7 |
I agree with you that portage should deal with it, and if I understood |
| 8 |
Finn correctly, I think he thinks like me, that most users will use a |
| 9 |
ppc-macos system and occasionaly use a ~ppc-macos package. |
| 10 |
|
| 11 |
My current setup is equal to this: my base install is ppc-macos and I |
| 12 |
test ~ppc-macos packages against that. Portage pulls whatever it needs |
| 13 |
for each package I test/keyword. I argue that I simulate a 'user' |
| 14 |
system this way. However, if some devs think you can only keyword |
| 15 |
~ppc-macos on a fully ~ppc-macos system, then I better stop, which I |
| 16 |
will until this is straightened out. The reason why this is brought up |
| 17 |
now, is because there is a package which doesn't compile on a ppc-macos |
| 18 |
system, but does on a ~ppc-macos system, because the output of emerge |
| 19 |
-ep system is different for {,~}ppc-macos. |
| 20 |
|
| 21 |
I still think that this difference in emerge -ep system is the actual |
| 22 |
problem, but I want to be very sure that my setup is accepted, which it |
| 23 |
apparently is not at the moment. Hence, I won't move a repoman commit |
| 24 |
muscle. |
| 25 |
|
| 26 |
|
| 27 |
Nick Dimiduk wrote: |
| 28 |
> I'm afraid I don't understand what (if anything) needs to be done. Care |
| 29 |
> to elaborate? |
| 30 |
> |
| 31 |
> -Nick Dimiduk |
| 32 |
|
| 33 |
-- |
| 34 |
Fabian Groffen |
| 35 |
Gentoo for Mac OS X |
| 36 |
-- |
| 37 |
gentoo-osx@g.o mailing list |
Archives