Built 14 Mac OS X dmg still defective (including quick fix) - Technical Help - Forum

Permalink

Posted at: 2010-02-03 06:57:18

Joined: 2010-02-03 06:43:59
Posts: 2

The "global"-folder is still missing in the Mac OSX- package. Somebody has marked the fault as fixed but has not updated the dmg-package yet.

This is just a quick fix for those who have Subversion installed on their system: http://subversion.apache.org/packages.html#osx

Assuming that Build 14 of Widelands is installed in your "Applications"- folder open the Terminal program and type in the following command

"sudo svn co https://widelands.svn.sourceforge.net/svnroot/widelands/trunk/global /Applications/Widelands.app/Contents/Resources/global"

You will be asked for an administrator password.

After that a message will come up:

Certificate information: - Hostname: *.svn.sourceforge.net - Valid: from Mon, 04 Jan 2010 14:21:55 GMT until Sat, 05 Feb 2011 09:03:23 GMT - Issuer: Equifax Secure Certificate Authority, Equifax, US - Fingerprint: ea:d1:3e:01:cc:16:e9:9b:c2:ab:4b:0c:cc:26:5f:25:78:ea:89:b4 (R)eject, accept (t)emporarily or accept (p)ermanently?

Press either "t" or "p".

This will add the missing global folder to your installed Widelands.app file. Well it works with svn4563-Version on my PPC running 10.5.8 at least.

HTH Ulf

Top

QCS

Permalink

Posted at: 2010-02-03 10:00:49

Joined: 2009-12-29 22:47:00
Posts: 99

Instead of "svn co" (for checkout) you can also use "svn export", which does the same, but doesn't clutter your installation folder with .svn metadata folders you don't need anyway. If someone can tell the revision which build14 is based on (or which tag has been set for the release), you can use the option -r <rev> to get the specific revision.

sudo svn export -r <rev> https://widelands.svn.sourceforge.net/svnroot/widelands/trunk/global /Applications/Widelands.app/Contents/Resources/global

Edit: Apparently the tag is called "build-14" so the following should also work:

sudo svn export https://widelands.svn.sourceforge.net/svnroot/widelands/tags/build-14/global /Applications/Widelands.app/Contents/Resources/global

Edited: 2010-02-03 10:07:09

Top

UlfBaur

Permalink

Posted at: 2010-02-03 15:33:22

Joined: 2010-02-03 06:43:59
Posts: 2

QCS wrote: Instead of "svn co" (for checkout) you can also use "svn export", which does the same, but doesn't clutter your installation folder with .svn metadata folders you don't need anyway. If someone can tell the revision which build14 is based on (or which tag has been set for the release), you can use the option -r <rev> to get the specific revision.

Sorry I can not find any subversion noise in the application folder as there is no SVN- clutter in or below the "global"- folder context. IMHO you will get the wanted files only. Can you tell me where I can find the .svn- metadata you are talking about?

And for the revision level the user should open the not working program to find out the revision level just to get the very same files he will get relying on the subversion internals?

Top

QCS

Permalink

Posted at: 2010-02-03 15:50:00

Joined: 2009-12-29 22:47:00
Posts: 99

Sorry I can not find any subversion noise in the application folder as there is no SVN- clutter in or below the "global"- folder context. IMHO you will get the wanted files only. Can you tell me where I can find the .svn- metadata you are talking about?

About SVN Metadata:

Every folder which origins in a "svn checkout" execution has a hidden folder ".svn". Every subfolder of this folder also has this hidden folder ".svn". SVN stores its metadata there, this is perfectly normal. SVN remembers there, for example, where it got those data from (SVN URL), which revision it was and so on. If you just need to complete your game installation due to a bug in the original packaging, you don't need these metadata folders, especially when you use the branch data (build-14) do complete your original build-14 installation.

The reason that you can't find these folders is possibly that you don't see hidden folders. Check your "file browsing utility" if it displays hidden folders, or use a command line to display those (e.g. "ls -la").

"svn checkout" creates those metadata folders for later use (e.g. commits, updates etc.), "svn export" doesn't.

And for the revision level the user should open the not working program to find out the revision level just to get the very same files he will get relying on the subversion internals?

No, that's why I already checked it and provided the solution below:

sudo svn export https://widelands.svn.sourceforge.net/svnroot/widelands/tags/build-14/global /Applications/Widelands.app/Contents/Resources/global

Top

Search

Donation

Login

Currently online