| 1 |
On 11/02/15 10:24, Greg Turner wrote: |
| 2 |
> Consider this hypothetical KEYWORDS specifier I generated merging some |
| 3 |
> gx86 and prefix content: |
| 4 |
> |
| 5 |
> KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc |
| 6 |
> ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd |
| 7 |
> ~ppc-aix ~x64-freebsd ~x86-freebsd ~hppa-hpux ~ia64-hpux ~x86-interix |
| 8 |
> ~amd64-linux ~ia64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos |
| 9 |
> ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris" |
| 10 |
> |
| 11 |
> I don't see a lot of stuff like the above ... well, anywhere. So ... |
| 12 |
> is it wrong? I'm at a loss as to why it would be. |
| 13 |
> |
| 14 |
> Perhaps, is it SOP to rely on prefixes accepting gx86 keywords from |
| 15 |
> non-prefix arch'es they correspond to? Doesn't that tend to defeat |
| 16 |
> the whole purpose of having prefix-specific keywords as we move toward |
| 17 |
> a single-shared-tree future? |
| 18 |
> |
| 19 |
> tia for any insights! |
| 20 |
> |
| 21 |
> -gmt |
| 22 |
> |
| 23 |
While the need for it is fading fast for me I always would |
| 24 |
have liked to have a ~ppc64-linux keyword. Going forward |
| 25 |
would suit me in that regard at least for the linux platform. |
| 26 |
For stuff like aix and other unixes in the prefix tree it may |
| 27 |
or may not be a good idea on a platform by platform basis. |
| 28 |
I can only judge for aix and macos. |
| 29 |
|
| 30 |
Francois |
Archives