| 1 |
All, |
| 2 |
|
| 3 |
I have been acting as a backup maintainer for dev-vcs/cli. A pull |
| 4 |
request was opened today that changes the way we detect whether the |
| 5 |
ebuild is live from looking for "live" in $PROPERTIES to the version |
| 6 |
number [1]. |
| 7 |
|
| 8 |
A different dev referred me to PMS which indicates that ebuilds should |
| 9 |
not rely on $PROPERTIES for anything [2]. |
| 10 |
|
| 11 |
I see quite a few ebuilds in the tree checking $FEATURES however, which |
| 12 |
imo is even less reliable since $FEATURES is not specified anywhere in pms |
| 13 |
and the $FEATURES variable is portage-specific. |
| 14 |
|
| 15 |
I guess I'm looking for consistency. If we are going to allow |
| 16 |
$FEATURES to be checked, should we allow $PROPERTIES to be checked? Or, |
| 17 |
should we ban checking both of them? |
| 18 |
|
| 19 |
IMO if we allow $FEATURES to be checked, we really should reword PMS to |
| 20 |
not say anything about $PROPERTIES other than to define the tokens it |
| 21 |
can contain. |
| 22 |
|
| 23 |
Thoughts? |
| 24 |
|
| 25 |
William |
| 26 |
|
| 27 |
[1] https://github.com/gentoo/gentoo/pull/15851 |
| 28 |
[2] https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-670007.3.5 |
Archives