On Tue, May 27, 2008 at 2:23 PM, Sebastian Nowicki <sebnow@gmail.com> wrote:
For some reason `file` on Mac OSX has different arguments than BSD and Linux; -i no longer prints out the mime strings. With the environment variable COMMAND_MODE set to "legacy", `file` behaves more like it does on Linux and BSD, i.e., `file -i` prints the mime type.
Signed-off-by: Sebastian Nowicki <sebnow@gmail.com> --- scripts/makepkg.sh.in | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 91b05f1..aa0b99e 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -32,6 +32,8 @@ # gettext initialization export TEXTDOMAIN='pacman' export TEXTDOMAINDIR='@localedir@' +# necessary to achieve consistent behavior for `file` on Mac OSX +export COMMAND_MODE=legacy Use '' (quotes) like every other variable here, but otherwise looks fine. I think this is the best solution to the problem. And concise is fine: # file -i is broken on Mac OSX unless legacy mode is set or at least I consider it broken. :)
myver='@PACKAGE_VERSION@' confdir='@sysconfdir@' -- Acked-by: Dan McGee <dan@archlinux.org>