Subject: Re: pkg/36257 (games/wesnoth has msgfmt problems (plurals) [NetBSD 3.0])
To: None <,,>
From: Christos Zoulas <>
List: pkgsrc-bugs
Date: 05/09/2007 18:55:03
The following reply was made to PR pkg/36257; it has been noted by GNATS.

From: (Christos Zoulas)
To:,,,, kre@munnari.OZ.AU
Subject: Re: pkg/36257 (games/wesnoth has msgfmt problems (plurals) [NetBSD 3.0])
Date: Wed, 9 May 2007 14:52:42 -0400

 On May 9,  6:50pm, kre@munnari.OZ.AU (Robert Elz) wrote:
 -- Subject: Re: pkg/36257 (games/wesnoth has msgfmt problems (plurals) [NetBS
 |  Aside from cases where you can rewrite things to simplify and avoid
 |  a logical operator completely, the only reason to avoid -a and -o 
 |  (using && and || instead) is to avoid strangeness in implementations of
 |  test.   If you were confident that test whatever -a whatever_else
 |  would have the same effect (always) as test whatever && test whatever_else
 |  then using the former would always be better - even where test is built
 |  into the shell, it means less work, and also allows test to cache stat
 |  results (in expressions like "test -b x -o -c x").
 You can always use parentheses:
     test \( -b x \) -o \( -c x \)
 I always use parentheses with -a and -o and have not encountered
 a test implementation that does not work properly.