[PATCH] Fix typos and shell for MacOSX packaging scripts

[Henrik Brautaset Aronsen]

Den 03.10.12 23:01, skrev Cristian Ionescu-Idbohrn:
> On Wed, 3 Oct 2012, Henrik Brautaset Aronsen wrote:
>> Den 03.10.12 21:12, skrev Cristian Ionescu-Idbohrn:
>>> What do:
>>>
>>> 	APPLECOLLATION
>>> 	APPLELOCALE
>>>
>>> show ona a MacOSX, anyway?  Worst case ;)
>> On my machine, these give:
>>
>> $ defaults read .GlobalPreferences AppleCollationOrder
>> nb
>> $ defaults read .GlobalPreferences AppleLocale
>> nb_NO
> Henrik har some answers, indeed :)  But I'd very much want to find out
> more, if possible.  Anyone?

There's some info at 
http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPInternational/Articles/LanguageDesignations.html#//apple_ref/doc/uid/20002144-BBCEGGFF

In short, both strings can be 2 to (at least) 10 characters long, with 
lower- and uppercase characters, underscores and dashes.

>> (By the way, I regret touching /bin/sh now.
> Well, you shouldn't.

I'm more and more convinced that I should.

>> IMHO it's a good idea to keep subsurface.sh as close to the original
>> gtk-mac-bundler/bundler/launcher.sh as possible.  That way it's easier
>> to merge changes when it changes.)
> I would be interested in looking at a copy of that file, please.

Google? :) 
https://github.com/jralls/gtk-mac-bundler/blob/master/bundler/launcher.sh

> Thing is, as it stands, '#!/bin/bash' is required.  The script would break
> if run under shells not supporting bashisms.

Thing is, I can't understand what's wrong with using bash here. Bash 
will be in OSX "forever", and we get the (fairly important) added bonus 
of easy merges when launcher.sh changes.

If we change subsurface.sh to something very different from launcher.sh, 
we lose that.

H