| 1 |
On Thu, 08 Mar 2012 09:07:18 -0800 |
| 2 |
Zac Medico <zmedico@g.o> wrote: |
| 3 |
> It's a very special metadata variable. Of course, it could also be |
| 4 |
> implemented in many different ways that do not involve bash variable |
| 5 |
> assingments. Maybe the differences between the various possible ways |
| 6 |
> truly make a difference to some people, but to me it's just |
| 7 |
> hair-splitting [1]. |
| 8 |
> |
| 9 |
> [1] http://en.wikipedia.org/wiki/Trivial_objections |
| 10 |
|
| 11 |
Having a different, special rule for something that looks exactly like |
| 12 |
lots of other things that do not have that different, special rule is |
| 13 |
hardly hair splitting. This rule would have to be documented and have |
| 14 |
special code to carefully enforce it. That's a big deal. |
| 15 |
|
| 16 |
Having something break because you add an unrelated comment to the top |
| 17 |
of a file is weird. |
| 18 |
|
| 19 |
Having something break because you indent it, where nothing else breaks |
| 20 |
if you do the same thing, is weird. |
| 21 |
|
| 22 |
Having something break because you make full use of bash syntax, where |
| 23 |
nothing else breaks if you do the same thing, is weird. |
| 24 |
|
| 25 |
There are already a whole pile of subtle traps for ebuild writers and |
| 26 |
complications for people learning the system. We should be aiming to |
| 27 |
reduce these, not add to them. |
| 28 |
|
| 29 |
-- |
| 30 |
Ciaran McCreesh |
Archives