| 1 |
The issue with the 'macos' keyword was discussed today in #gentoo-dev. |
| 2 |
For those who were not present, here is a brief summary of the findings: |
| 3 |
|
| 4 |
According to GLEP 22, the current 'macos' keyword would need to be |
| 5 |
divided into four keywords: |
| 6 |
ppc-mach-bsd-libsystem |
| 7 |
ppc64-mach-bsd-libsystem |
| 8 |
ppc-mach-bsd-libsystem-macos |
| 9 |
ppc64-mach-bsd-libsystem-macos |
| 10 |
|
| 11 |
The fifth field "distribution", is not part of GLEP 22, however it was |
| 12 |
discussed that both macos as well as bsd would need the fifth field to |
| 13 |
differentiate between different operating environments. For example, |
| 14 |
adium is a net-im application which works on macos, but would not work |
| 15 |
on pure darwin. Porting portage to other linux distributions would fall |
| 16 |
under this same category. For example, x86-linux-gnu-glibc-suse. |
| 17 |
|
| 18 |
The obvious problem with adding yet another field to the keyword |
| 19 |
specification is the large amount of resulting keywords. Regex, macros |
| 20 |
and exploding keywords were discussed as possible solutions. The latter |
| 21 |
was determined to be the least painful. For example, the four keywords |
| 22 |
for macos would become: |
| 23 |
ppc{,64}-bsd-mach-libsystem{,-macos} |
| 24 |
|
| 25 |
Before proposing an amendment to GLEP 22 to this effect, it might be |
| 26 |
useful to have some prior discussion on this list. The gentoo-osx team |
| 27 |
will be postponing the conversion of the 'macos' keyword until these |
| 28 |
matters are agreed upon. |
| 29 |
|
| 30 |
--j4rg0n && gongloo |
| 31 |
Gentoo-OSX Ebuild Leads |
| 32 |
|
| 33 |
-- |
| 34 |
gentoo-dev@g.o mailing list |
Archives