| 1 |
On 09-10-2008 08:39:59 +0200, Michael Haubenwallner wrote: |
| 2 |
> Depends on the definition: |
| 3 |
> x86: "Gentoo Linux" |
| 4 |
> x86-linux: "non-prefixed Gentoo on any Linux" |
| 5 |
> x86+linux: "Gentoo Prefix on any Linux" |
| 6 |
> |
| 7 |
> The *+* is only because there is non-Prefix *-fbsd already. |
| 8 |
> |
| 9 |
> And "Gentoo Linux" != "non-prefixed Gentoo on any Linux" != "Gentoo |
| 10 |
> Prefix on any Linux" |
| 11 |
> |
| 12 |
> The problem is how to distinguish |
| 13 |
> between "non-prefixed Gentoo on FreeBSD" (keyword "*-fbsd") |
| 14 |
> and "Gentoo Prefix on FreeBSD" (keyword "*-fbsd" in Prefix ATM) |
| 15 |
|
| 16 |
Not a problem, as in Prefix, it would be x86-freebsd, because people |
| 17 |
convinced me that fbsd is too short and causing inconsistencies, because |
| 18 |
nbsd or obsd would have multiple candidates. |
| 19 |
|
| 20 |
> > Yeah, and to me still an overloading of the keywording thing with Prefix |
| 21 |
> > stuff. PROPERTIES=prefix would be more to my liking. |
| 22 |
> |
| 23 |
> Ok with me eventually to indicate prefix-awareness, but it does not fix |
| 24 |
> the *-fbsd (prefix <> non-prefix) problem, as they still would share the |
| 25 |
> same keyword. |
| 26 |
|
| 27 |
see above. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Fabian Groffen |
| 32 |
Gentoo on a different level |
Archives