On Fri, 2005-04-02 at 00:54 +0000, Ciaran McCreesh wrote: > On Thu, 03 Feb 2005 19:45:27 -0500 Olivier Cr�te <[EMAIL PROTECTED]> > wrote: > | On Fri, 2005-04-02 at 00:00 +0000, Ciaran McCreesh wrote: > | > Just a note on how to do if / then / else blocks properly in bash... > | > The following style *won't* work, so don't do anything daft like > | > committing it to eutils.eclass without testing and h0rking half the > | > tree, okay? > | > | But no sane developer would commit to an eclass without testing all > | ebuilds that it might affect, so that's not really a problem. (And > | that explains why no versioning is needed for eclasses) > > If someone's dumb enough to commit a syntax error in an eclass then > everything that sources that eclass breaks all the time. You'd get > zillions of errors on a simple 'emerge sync'. But then, since everyone > tests everything before committing, this is all hypothetical.
Like ChrisWhite... -- Olivier Cr�te [EMAIL PROTECTED] Gentoo Developer x86 Security Liaison
signature.asc
Description: This is a digitally signed message part
