| 1 |
В Чтв, 16/09/2010 в 17:44 +0200, Jeroen Roovers пишет: |
| 2 |
> On Thu, 16 Sep 2010 09:41:30 -0500 |
| 3 |
> Jeremy Olexa <darkside@g.o> wrote: |
| 4 |
> |
| 5 |
> > * econf doesn't need to "|| die" |
| 6 |
> |
| 7 |
> Is that a novelty change? Most of the tree still does econf || die ... |
| 8 |
|
| 9 |
econf is function that dies on its own. |
| 10 |
|
| 11 |
But still there is one case where || die after econf can be useful - |
| 12 |
very-very long list of econf options you have to edit rather frequently. |
| 13 |
|
| 14 |
econf \ |
| 15 |
parameter1 \ |
| 16 |
parameter2 \ |
| 17 |
... \ |
| 18 |
parameterN || die |
| 19 |
|
| 20 |
In case || die is absent and developer forgot '\' at the end of line |
| 21 |
portage will not abort build: econf with shortened list of options will |
| 22 |
succeed and next most probably absent command `parameterk parameter$((k |
| 23 |
+1)) ... parameterN` will have no || die at the end. In general case || |
| 24 |
die after econf is redundant and should be dropped. |
| 25 |
|
| 26 |
-- |
| 27 |
Peter. |
Archives