| 1 |
On Thu, 2012-03-08 at 16:29 +0000, Ciaran McCreesh wrote: |
| 2 |
> And you believe that having exactly one place inside ebuild text where |
| 3 |
> there are different whitespace, quoting and indenting rules for |
| 4 |
> something that otherwise looks exactly like any other metadata variable |
| 5 |
> isn't going to cause problems? |
| 6 |
|
| 7 |
In light of the fact that all 29758 ebuilds in portage already satisfy |
| 8 |
the proposed whitespace, quoting, and indenting constrains on EAPI |
| 9 |
assignment, the probability of problems appears to be vanishingly small. |
| 10 |
And "vanishingly small" and can be reduced to zero by simply adding a |
| 11 |
check to repoman. |
| 12 |
|
| 13 |
Can you come up with a sane scenario under which an ebuild writer would |
| 14 |
want to use a different syntax for setting EAPI? |
| 15 |
|
| 16 |
-Alexandre |
Archives