| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Lina Pezzella schrieb: |
| 5 |
| The issue with the 'macos' keyword was discussed today in #gentoo-dev. |
| 6 |
| For those who were not present, here is a brief summary of the findings: |
| 7 |
| |
| 8 |
| According to GLEP 22, the current 'macos' keyword would need to be |
| 9 |
| divided into four keywords: |
| 10 |
| ppc-mach-bsd-libsystem |
| 11 |
| ppc64-mach-bsd-libsystem |
| 12 |
| ppc-mach-bsd-libsystem-macos |
| 13 |
| ppc64-mach-bsd-libsystem-macos |
| 14 |
|
| 15 |
~From GLEP 22: |
| 16 |
"Each keyword needs to specify, either explicitly or implicitly, the |
| 17 |
following parameters: ARCH, USERLAND, LIBC, and KERNEL.[...] |
| 18 |
A fully-specified keyword would look like "ARCH-KERNEL-USERLAND-LIBC", |
| 19 |
[...]" |
| 20 |
|
| 21 |
A 5th parameter isn't mentioned in GLEP 22, neither is the order which |
| 22 |
you mentioned in the first place. |
| 23 |
|
| 24 |
| The fifth field "distribution", is not part of GLEP 22, however it was |
| 25 |
| discussed that both macos as well as bsd would need the fifth field to |
| 26 |
| differentiate between different operating environments. For example, |
| 27 |
| adium is a net-im application which works on macos, but would not work |
| 28 |
| on pure darwin. |
| 29 |
Well, i would put this into the USERLAND part: |
| 30 |
ppc[64]-mach-macos-libsystem |
| 31 |
ppc[64]-mach-darwin-libsystem |
| 32 |
|
| 33 |
Mac OSX userland _is_ different from bsd userland, so just put it there. |
| 34 |
|
| 35 |
Porting portage to other linux distributions would fall |
| 36 |
| under this same category. For example, x86-linux-gnu-glibc-suse. |
| 37 |
|
| 38 |
That keyword is imho nonsense: a keyword shall distinguish between |
| 39 |
premisses. I can't imagine a situation, in which an application would |
| 40 |
refuse to work under SUSE linux because it is SUSE, apart from missing |
| 41 |
dependencies. But the keyword should not be about package dependencies ! |
| 42 |
|
| 43 |
| The obvious problem with adding yet another field to the keyword |
| 44 |
| specification is the large amount of resulting keywords. Regex, macros |
| 45 |
| and exploding keywords were discussed as possible solutions. The latter |
| 46 |
| was determined to be the least painful. For example, the four keywords |
| 47 |
| for macos would become: |
| 48 |
| ppc{,64}-bsd-mach-libsystem{,-macos} |
| 49 |
|
| 50 |
According to GLEP22 (again) this should be: |
| 51 |
{ppc,ppc64}-mach-{bsd,macos,darwin}-libsystem |
| 52 |
|
| 53 |
| Before proposing an amendment to GLEP 22 to this effect, it might be |
| 54 |
| useful to have some prior discussion on this list. The gentoo-osx team |
| 55 |
| will be postponing the conversion of the 'macos' keyword until these |
| 56 |
| matters are agreed upon. |
| 57 |
|
| 58 |
I don't think we need an amendment, GLEP 22 is sufficient for this. |
| 59 |
|
| 60 |
.02 EUR |
| 61 |
|
| 62 |
- -- |
| 63 |
Danny van Dyk |
| 64 |
Gentoo/AMD64 Developer |
| 65 |
kugelfang@g.o |
| 66 |
-----BEGIN PGP SIGNATURE----- |
| 67 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 68 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 69 |
|
| 70 |
iD8DBQFBBY4aaVNL8NrtU6IRAgilAJ9Gbvv2wlyyqzmWcjwTdN0MqEn9jgCfaQAk |
| 71 |
Kv7gB8OaVxUP62KUj2M2Pho= |
| 72 |
=l2B/ |
| 73 |
-----END PGP SIGNATURE----- |
| 74 |
|
| 75 |
-- |
| 76 |
gentoo-dev@g.o mailing list |
Archives