| 1 |
On Monday 01 October 2007, Alin Năstac wrote: |
| 2 |
> Donnie Berkholz wrote: |
| 3 |
> > On 11:30 Sun 30 Sep , Alin Nastac (mrness) wrote: |
| 4 |
> >> 1.1 mail-filter/dspam/dspam-3.8.0-r7.ebuild |
| 5 |
> >> |
| 6 |
> >> file : |
| 7 |
> >> http://sources.gentoo.org/viewcvs.py/gentoo-x86/mail-filter/dspam/dspam- |
| 8 |
> >>3.8.0-r7.ebuild?rev=1.1&view=markup plain: |
| 9 |
> >> http://sources.gentoo.org/viewcvs.py/gentoo-x86/mail-filter/dspam/dspam- |
| 10 |
> >>3.8.0-r7.ebuild?rev=1.1&content-type=text/plain if use mysql || use |
| 11 |
> >> postgres ; then |
| 12 |
> >> myconf="${myconf} --enable-preferences-extension" |
| 13 |
> >> fi |
| 14 |
> > |
| 15 |
> > I think you could use use_enable() or use_with() for many of these. |
| 16 |
> > |
| 17 |
> > $(use mysql || use postgres && use_enable virtual-users) |
| 18 |
> |
| 19 |
> According to bash manual, && has a greater precedence than ||. That |
| 20 |
> would translate in: |
| 21 |
|
| 22 |
i think i buy into Don Libes' philosophy ... use proper parentheses and |
| 23 |
operator precedence be damned ... if you have to look up the relationship of |
| 24 |
operators to make sure things are kosher, then chances are someone else wont |
| 25 |
and will screw it up. whatever precedence language $x has, chances are it |
| 26 |
wont match exactly language $y, so break out the () loving. |
| 27 |
-mike |
Archives