| 1 |
On Nov 29, 2007, at 12:04 , Michael Haubenwallner wrote: |
| 2 |
|
| 3 |
> On Thu, 2007-11-29 at 10:38 +0100, Johan Hattne wrote: |
| 4 |
> |
| 5 |
>> I'm not so sure. AND takes precedence over OR, so |
| 6 |
> |
| 7 |
> Nope, 'man bash' says: |
| 8 |
> |
| 9 |
> Of these list operators, && and || have equal precedence, |
| 10 |
> followed by ; and &, which have equal precedence. |
| 11 |
|
| 12 |
Sorry, I should have checked that! My mistake! |
| 13 |
|
| 14 |
>> |
| 15 |
>> a && b || c |
| 16 |
>> |
| 17 |
>> is equivalent to |
| 18 |
>> |
| 19 |
>> ( a && b ) || c |
| 20 |
> |
| 21 |
> Yes, but |
| 22 |
> |
| 23 |
> a || b && c |
| 24 |
> |
| 25 |
> also is equivalent to |
| 26 |
> |
| 27 |
> ( a || b ) && c |
| 28 |
> |
| 29 |
|
| 30 |
But I still believe that what we have tk is broken |
| 31 |
|
| 32 |
[[ ${CHOST} != *-darwin* ]] && sed -i \ |
| 33 |
-e "s,^\(TK_CC_SEARCH_FLAGS='.*\)',\1:${EPREFIX}/usr/$ |
| 34 |
{mylibdir}'," \ |
| 35 |
-e "s,^\(TK_LD_SEARCH_FLAGS='.*\)',\1:${EPREFIX}/usr/$ |
| 36 |
{mylibdir}'," \ |
| 37 |
"${ED}"/usr/${mylibdir}/tkConfig.sh || die |
| 38 |
|
| 39 |
because it'll die if CHOST isn't darwin OR if the sed fails. In my |
| 40 |
case CHOST is darwin. |
| 41 |
|
| 42 |
// Cheers; Johan |
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-alt@g.o mailing list |
Archives