| 1 |
On 11-02-2006 20:05:58 +0000, Ciaran McCreesh wrote: |
| 2 |
> On Sat, 11 Feb 2006 08:28:34 +0100 Grobian <grobian@g.o> wrote: |
| 3 |
> | > kfreebsd-gnu is, in effect, one example you're using already. You'd |
| 4 |
> | > have x86 as the arch, FreeBSD as the kernel and GNU as the userland. |
| 5 |
> | |
| 6 |
> | Yes, but you're actually mixing two things here now. The right hand |
| 7 |
> | side of the 2-tuple is not a kernel or userland, it is an OS, which |
| 8 |
> | includes this in itself. |
| 9 |
> |
| 10 |
> Mmmmmm. I'm not convinced that that justifies creating weird codes for |
| 11 |
> the weird cases... |
| 12 |
|
| 13 |
Ok. If we're on the same wave length here, then I think the real |
| 14 |
question is here whether we do allow hyphens to be in the os part or |
| 15 |
not. If yes, the part till the first hyphen is the arch, and everything |
| 16 |
from the hyphen (exclusive) till the end of string is the os part. If |
| 17 |
no, an 'escape' method must be defined for the os part. In both cases |
| 18 |
it is necessary to state that the arch cannot contain hyphens in it, and |
| 19 |
if such restriction is defined, it might be handy to immediately add |
| 20 |
spaces and the like to the list. |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Fabian Groffen |
| 25 |
Gentoo/Alt |
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives