| 1 |
Ühel kenal päeval, E, 27.03.2017 kell 11:07, kirjutas Fabian Groffen: |
| 2 |
> On 27-03-2017 09:56:50 +0200, Ulrich Mueller wrote: |
| 3 |
> > > > > > > On Mon, 27 Mar 2017, Fabian Groffen wrote: |
| 4 |
> > > > > When you say "arch" you actually mean a keyword as per GLEP- |
| 5 |
> > > > > 53[1] |
| 6 |
> > > > > right? |
| 7 |
> > > > |
| 8 |
> > > > Which doesn't agree with actual usage in the tree, though. |
| 9 |
> > > That surprises me. Do you have an example of that? |
| 10 |
> > |
| 11 |
> > The GLEP says about the OS suffix: |
| 12 |
> > |
| 13 |
> > "The right hand part indicates the operating system or |
| 14 |
> > distribution, |
| 15 |
> > such as linux, macos, solaris or fbsd. If the right hand part is |
| 16 |
> > omitted, it implies the operating system/distribution type is |
| 17 |
> > GNU/Linux." |
| 18 |
> > |
| 19 |
> > So if I understand this correctly, x86-linux should be equivalent |
| 20 |
> > to |
| 21 |
> > x86. But in reality, the linux suffix denotes that it is a prefix |
| 22 |
> > arch. I'm not saying that this is bad, only it's not what the GLEP |
| 23 |
> > says. |
| 24 |
> |
| 25 |
> I see. The lack of explicit mentioning what the difference means |
| 26 |
> allows |
| 27 |
> for different interpretations. I always *assumed* it meant Gentoo (1 |
| 28 |
> part) vs Gentoo/Alt (2 parts). |
| 29 |
> |
| 30 |
> > Until recently there was also x64-freebsd vs amd64-fbsd, where both |
| 31 |
> > the arch and the OS part denoted the same, but used different |
| 32 |
> > tokens |
| 33 |
> > to distinguish between prefix and non-prefix. (And I don't |
| 34 |
> > understand |
| 35 |
> > why amd64 is called x64 on prefix. A different OS suffix should be |
| 36 |
> > sufficient.) |
| 37 |
> |
| 38 |
> It kind of proves the point that two fields in a keyword isn't |
| 39 |
> "enough |
| 40 |
> for everyone". |
| 41 |
> |
| 42 |
> Back to the topic of the thread, is it possible to make the |
| 43 |
> difference |
| 44 |
> between e.g. x86, x86-linux, x86-solaris and x86-macos in this |
| 45 |
> proposal? |
| 46 |
> |
| 47 |
|
| 48 |
I believe the intention here is for this file to declare stuff about an |
| 49 |
"arch" in terms of what repoman names it as such (--include-arches=, |
| 50 |
etc), and what profiles.desc has as the first column value (in comments |
| 51 |
it also names that column "arch"). |
| 52 |
The filename "arches.desc" just comes from that convention, while |
| 53 |
indeed it really matches what you put in KEYWORDS in terms of ebuild |
| 54 |
usage. I guess that filename is a shed to paint then too. |
| 55 |
|
| 56 |
|
| 57 |
Mart |
Archives