i have no freaking clue what im doing. i downloaded some file got a .tgz or whatever, gunzipped or whatever it and i've got a folder with lots of makefiles and stuff and seriously, i'm ready to slash my wrists. could anyone please just do a step-by-step on installing this to a ubuntu that i have access to as sudo su and stuff (root access). i tried to download the .package and when i start that, i get this:
esa@ubbis:~/schism$ sh schism-0.5.x86.package
schism-0.5.x86.package: 32: Syntax error: "(" unexpected (expecting "fi")
ok i've gunzipped and tar x'd the resultant .tar
, or at least i tried with tar x apckage.
i give up!!
please assist me, i have no way of finding this thing out and the ubuntu forums are useless when it comes to this.
i dunno, tar -x cvs-snapshot.tar doesnt do anything either.
i'd ask on thei rcchannel but i've misplaced which server it was on, or is the esper.net #schism dead?
well i got tar xvf to do it but i still cant compile jack shit, it keeps complaining of CPP or something, i dont know, bah!
help!!
wow i did a apt-get install schism and now it installed something. but its a old 0.5rc1 or something, i dont know. im gonna try and find oujt where schism is, and untar the contents to that and wish for the best. right? i hope so!
>>4136
That'll probably make crap of your schism installation. That way you must also find out where the packager made all the files go. Just uninstall that old package. Sometimes Schism has a lot of updates and it doesnt pay off to wait for the packager to come in action. Besides that, Mrsbrisby supplies autopackages (which fail on your system for some reason). Ubuntu just sucks. The auto installer never failed on me.
Just do this after you uninstalled the aptpackage
$tar xzvf cvs-snapshot.tgz
$cd schism2/
$./configure && make && make install
$schismtracker
That should do it.
>>4133
AFAIK there never was a schism channel on espernet. Reduz had cheesetracker there. Schism is on freenode
or just mark executable and run:
./schism-0.5.x86.package>>4139
That would imply "just" running two commands instead of one. ;)
There's something called glick (http://www.gnome.org/~alexl/glick/) that might help this in the future.
>>4142
Help what? Create another opaque structure that does a bunch of hidden magic so that people who know what they're doing can't otherwise manipulate the package?
Welcome to Linux, learn how to build from source. It's just the way things are, and it's the way things should be.
>>4143 Tools simply help people accomplish goals: glick is just a loopback-mounted filesystem, but it is receiving gnome-support where autopackage isn't, as a result it may be easier to use glick in the future than it presently is to use autopackage.
>>4144
I still say 'bash schism-0.5.x86.package' is simpler than 'chmod +x schism-0.5.x86.package && ./schism-0.5.x86.package'. External tools don't change that fact.
>>4145 Oh I agree, which is why glick puts a shell-script header on it. It just doesn't "install" anywhere, it simply mounts, runs, and unmounts behind when done. It has special hooks so that file managers can make a proper icon for it, and know about file types, etc.