On 11 April 2013 22:50, Mike Caron <[email protected]> wrote: > On Thu, Apr 11, 2013 at 6:03 AM, Ralph Versteegen <[email protected]> > wrote: >> >> Popped in to celebrate with us? :) > > > Perhaps! > >> >> On 11 April 2013 13:44, James Paige <[email protected]> wrote: >> > Hello, Mike! >> > >> > Actually, maybe we can avoid tar. I know we had reasons in the past, but >> > they might have all evaporated by now. Originally I remember only >> > wanting to use tools likely to be already installed on Linux/Mac, but >> > Windows is the trouble-platform, and we have to bundle/download tools >> > anyway. It is worth thinking over. >> >> I think the two reasons for using tar were to preserve executable file >> bits and to preserve symlinks. Funny enough, tar.exe doesn't do either >> properly. >> >> I looked through the commandline options that 7za supports and saw >> nothing for file attributes or symlinks. So we're seemingly still >> better off using tar.exe, at least for creating tars. Which maybe we >> don't want to do. > > > Wait, you're using a Windows binary to create an archive with symlinks and > permission bits on Windows? Where do you get the symlinks in the first > place?? If you're going to do that, you would need cygwin or something, > whose tar command is presumably not broken.
Although we can't create a tar file containing symlinks (a possible work around could have been to start with a tar file containing symlinks and add new files to it. Unfortunately we also wanted to rename "OHRRPGCE-Game.app" to "gamename.app", which wasn't possible) we at least hoped to be able to extract files containing symlinks (duplicating the files) but that was broken too! How does cygwin store file attributes anyway, I wonder? I believe it stores symlinks as files (similar to the way Unix actually does, or to Windows .lnk files) >> >> >> Or, alternately the tar format doesn't seem that complicated. Maybe >> >> a >> >> highly specialized version is in order? >> > >> > These sound like the words of a man who hasn't read any tar file format >> > docs... or maybe I should say those sound like the words *I* spoke >> > before I had read any tar file format docs :) >> >> Yes, just look at what happened to tar.exe when it tried to read BSD >> tar files! This is an ancient file format seemingly with some weird >> quirks. > > > I realized, too late of course, that I forgot the ";)" I meant to add. I > would never seriously advocate trying to re-implement a program with such... > let's call it "legacy". We actually were seriously considering it before having looked at the file format! >> > --- >> > James >> > >> > On Wed, Apr 10, 2013 at 08:22:24PM -0400, Mike Caron wrote: >> >> Hi guys, long time no see. >> >> Is there some reason you're still using tar? Wouldn't it be easier >> >> to just >> >> bundle 7zip or something? I understand that it supports tar. >> >> Probably a >> >> few other formats too. You can obtain the console version here. >> >> Or, alternately the tar format doesn't seem that complicated. Maybe >> >> a >> >> highly specialized version is in order? >> >> >> >> On Wed, Apr 10, 2013 at 1:29 PM, James Paige >> >> <[email protected]> >> >> wrote: >> >> >> >> On Wed, Apr 10, 2013 at 09:52:23AM -0700, James Paige wrote: >> >> > I was almost finished releasing beelzebufo, when I was puzzled >> >> and >> >> > displayed to discover that Mac App game bundles build on Windows >> >> do >> >> not >> >> > work. If you build them on mac, they work fine. >> >> > >> >> > Here is the crash message: >> >> > >> >> > http://pastebin.com/jhu5H4b8 >> >> > >> >> > It looks like the problem has something to do with the SDL >> >> framework, >> >> > but I don't understand how this would fail on windows because >> >> there >> >> are >> >> > no more symlinks. >> >> >> >> "dismayed" not "displayed" >> >> >> >> I took the working app build on a Mac and compared it to the >> >> broken app >> >> built on Windows. I discovered that >> >> >> >> Contents/FrameWorks/SDL_mixer.framework/Versions/A/Frameworks/mikmod.framework >> >> is empty in the broken app. >> >> >> >> I tested tar.exe from the command line, and discovered that when >> >> it >> >> unpacks ohrrpgce-mac.minimal.tar it incorrectly unpacks several of >> >> the >> >> subfolders into the current directory, instead of where they >> >> belong >> >> under the OHRRPGCE-Game.app folder heirarchy. >> >> >> >> So the short answer is that this bug is, yet again, another >> >> instance of >> >> the windows port of tar.exe being a worthless piece of crap :( >> >> --- >> >> James >> >> _______________________________________________ >> >> Ohrrpgce mailing list >> >> [email protected] >> >> >> >> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org >> >> >> >> -- >> >> Mike Caron >> > >> >> _______________________________________________ >> >> Ohrrpgce mailing list >> >> [email protected] >> >> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org >> > >> > _______________________________________________ >> > Ohrrpgce mailing list >> > [email protected] >> > http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org >> _______________________________________________ >> Ohrrpgce mailing list >> [email protected] >> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org > > > > > -- > Mike Caron > > _______________________________________________ > Ohrrpgce mailing list > [email protected] > http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org > _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
