[Quadzmodo]

Does anyone know how to unzip the Limeware software for OS X?

[Mactoid]

That huge file that comes with limewire is actually a shell script w/data that self decompresses itself. Pretty nifty, IMHO
Anyway, to decompress it, just run it in from the terminal.

Edit: Just occured to me that you need to make the file executable before you can run it. to do that do chmod a+x LimeWireMacOSX.sh then to run it do ./LimeWireMacOSX.sh

[ 06-03-2001: Message edited by: Mactoid ]

[bil207]

There is also an easy install version if your still having problems. http://www.versiontracker.com/moreinfo.fcgi?id=10275

[wr11]

Check out the thread a better LimeWire for OSX! for a kewl way of packaging the regular limewire client for OSX. It works without the terminal and has a great icon IMHO.

[ 06-04-2001: Message edited by: wr11 ]

[dfbennett]

Originally posted by Mactoid:
<STRONG>That huge file that comes with limewire is actually a shell script w/data that self decompresses itself. Pretty nifty, IMHO
Anyway, to decompress it, just run it in from the terminal.

Edit: Just occured to me that you need to make the file executable before you can run it. to do that do chmod a+x LimeWireMacOSX.sh then to run it do ./LimeWireMacOSX.sh

[ 06-03-2001: Message edited by: Mactoid ]</STRONG>

why do you need to do that command? When I installed it I just did sh limewire.sh and it ran the installer. Then once it installed i just went to the folder and typed ./Limewire What's the difference between what I did and what you suggest?

[Mactoid]

Originally posted by dfbennett:
<STRONG>why do you need to do that command? When I installed it I just did sh limewire.sh and it ran the installer. Then once it installed i just went to the folder and typed ./Limewire What's the difference between what I did and what you suggest?</STRONG>

actually nothing really. I though to change it after posting but didn't bother. What I did was set the files executable bit so that I could run it like anyother command (the shell looks at the first line of the code to determine what to interpret the script with). You're method works just as well, but you directly tell the interpreter to run the file.

I made the suggestion to make the script executable, since that is what I always do first thing when I get a script so that I can always in the future execute it directly.

[dfbennett]

Originally posted by Mactoid:
<STRONG>

actually nothing really. I though to change it after posting but didn't bother. What I did was set the files executable bit so that I could run it like anyother command (the shell looks at the first line of the code to determine what to interpret the script with). You're method works just as well, but you directly tell the interpreter to run the file.

I made the suggestion to make the script executable, since that is what I always do first thing when I get a script so that I can always in the future execute it directly.</STRONG>

Cool thanks for the info. I wasn't trying to come off snide in that post and it may have seemed so. I'm just really new to this whole unix thing and i'm trying to learn what some of the commands do. Thanks for the clarification.