| 1 |
On 20-09-2019 22:53:53 +0200, Michał Górny wrote: |
| 2 |
> On Fri, 2019-09-20 at 13:46 -0700, Zac Medico wrote: |
| 3 |
> > |
| 4 |
> > If we take this underscore rule to its logical extreme, then we should |
| 5 |
> > rename python_targets_python3_7 to python_targets_python3-7, yes? |
| 6 |
> |
| 7 |
> Believe me, I would have done that already if not the fact that with all |
| 8 |
> the dependency logic around here it would be totally destructive to all |
| 9 |
> Gentoo systems. |
| 10 |
|
| 11 |
Honestly, with this reasoning, why force other packages to go through |
| 12 |
USE-flag renaming in that case? A major consumer of USE_EXPAND isn't |
| 13 |
sticking to the rule, which makes any benefit of it moot. Tools cannot |
| 14 |
assume the last underscore separates the USE_EXPAND var from its value, |
| 15 |
users cannot see what is the value either, without knowledge. |
| 16 |
|
| 17 |
Why not teach our tools (equery, quse, etc.) to print these USE-flags |
| 18 |
like Portage does? (looking them up to be valid expands) |
| 19 |
Then users have nothing to be confused about (no distinction between |
| 20 |
foo_bar and FOO="bar"), and new USE_EXPANDS cannot be |
| 21 |
silently/accidentially introduced. |
| 22 |
|
| 23 |
> But hey, expect hyphen on 3.8. |
| 24 |
|
| 25 |
I honestly feel for consistency and not confusing users, we should |
| 26 |
either do them all or stick to the current scheme. |
| 27 |
|
| 28 |
Thanks, |
| 29 |
Fabian |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Fabian Groffen |
| 34 |
Gentoo on a different level |
Archives