В Чтв, 16/09/2010 в 17:44 +0200, Jeroen Roovers пишет:
> On Thu, 16 Sep 2010 09:41:30 -0500
> Jeremy Olexa <[email protected]> wrote:
>
> > * econf doesn't need to "|| die"
>
> Is that a novelty change? Most of the tree still does econf || die ...
econf is function that dies on its own.
But still there is one case where || die after econf can be useful -
very-very long list of econf options you have to edit rather frequently.
econf \
parameter1 \
parameter2 \
... \
parameterN || die
In case || die is absent and developer forgot '\' at the end of line
portage will not abort build: econf with shortened list of options will
succeed and next most probably absent command `parameterk parameter$((k
+1)) ... parameterN` will have no || die at the end. In general case ||
die after econf is redundant and should be dropped.
--
Peter.
