Installing games not found in Gslapt?

[wackpanther]

Hi
Just wondering how I can add games and things that are not listed in Gslapt.
I want to play Warzone 2100
I have a tar.xz file, but I don't really know what to do with it
Thanks a lot for any help
B

[mimosa]

Try Sourcery - check the 'Get information' button first.

See the User Guide section on package management:

http://docs.salixos.org/wiki/Salix_Startup_Guide

If you do want to install something from source, it may be quite straightforward, or rather complicated. You will need to make sure yourself any required dependencies are installed first, whereas Salix's package management system deals with this for you.

The first step is to unpack the tarball and look for files like README and INSTALL that have instructions. In this case, though, there is a buildscript avaialble from http://slackbuilds.org ; Sourcery is Salix's graphical "front end" to that repository.

[wackpanther]

Thanks for replying
Can you tell me how to find Sourcery?
It doesn't appear to be on my computer- not in the menu, can't run as a command, also not in Gslapt or SlackBuilds.org.
I looked in the start up guide and tried to use SlackBuilds.org to get the corresponding archive for the game.
Following the instructions, I came up with a funny error when trying to execute the build.
After extracting my slackbuild file in the same folder as the .tar.xz source file for this game, I tried to install using terminal.

While logged in as a regular user, I can execute the slackbuild using
'warzone2100.SlackBuild'
and it starts listing a whole bunch of files.
Eventually I get

chown: changing ownership of `./m4': Operation not permitted
chown: changing ownership of `./COPYING.NONGPL': Operation not permitted
chown: changing ownership of `./install-sh': Operation not permitted
chown: changing ownership of `./ylwrap': Operation not permitted
chown: changing ownership of `.': Operation not permitted

ect...

So I figured I had to switch user to root.
But then with the same exact command, I get

command not found

What am I doing wrong?
There's something on the slackbuilds.org site about "a true login shell in order to have a correctly populated environment."
It says to try 'su -l' when switching to root, but that's not working for me.

It goes on with
" source the /etc/profile script after doing "su", or perhaps modifying /root/.bashrc to include necessary PATH elements."

But that is over my head at this stage.
Thank you for helping out new guy!

[knome]

I am running version 14.0, Xfce desktop, so the following may or may not be relevant depending on your installation...

In the menu, Sourcery is at Menu > System > Sourcery SlackBuild Manager

The command to start Sourcery is gksu sourcery

In Gslapt, Sourcery is listed as sourcery

[wackpanther]

Can anyone tell me why entering 'chemtool.SlackBuild' in the Terminal will result in an attempted compile while I'm logged in as user, but gives me 'Command Not Found' when logged in as root?
I'm Really not understanding this whole slackware thing

[wackpanther]

Also- Sourcery doesn't seem to exist anywhere.
I just can't find it!
It is not in the menu.
Entering 'gksu sourcery' gets me 'command not found'
Sourcery is not listed in gslapt or slapt-get.
It isn't in SlackBuilds.org.
Where can I find it?
Thanks!

[sqlpython]

Read here
http://docs.salixos.org/wiki/Sourcery

[laprjns]

Also- Sourcery doesn't seem to exist anywhere.
I just can't find it!
It is not in the menu.
Entering 'gksu sourcery' gets me 'command not found'
Sourcery is not listed in gslapt or slapt-get.
It isn't in SlackBuilds.org.
Where can I find it?
Thanks!

Let's deal with this issue first, then we can move on to your other questions. Sourcery / slapt-src are included as part of the Salix installation by default and are also available in the gslapt repository, so if you cannot find them on your system, then you either have a problem with you Salix installation or you somehow removed the packages. Can you please provide the following information:
1) What version of Salix are you using?
2) How did you install it? (iso install by cd, usb or livecd or did you upgrade from a prior Salix version)
3)Have you made any other custom configurations changes or installed 3rd party packages?

Also please post the output of the following command, you will need to be root to do this or you can use gksu:

Code: Select all

rich[~]$ gksu slapt-get --search  slapt-src

You should get something like this:

Code: Select all

slapt-src-0.3.2e-x86_64-2gv [inst=yes]: slapt-src (slapt slackbuild utility)
sourcery-0.9.2-noarch-1gv [inst=yes]: sourcery (a GTK+2 frontend to slapt-src)

If it's true that sourcery and slapt-src are not installed you will see "[inst=no]" instead of what's shown above. You can install them with the following command:

Code: Select all

gksu slapt-get --install sourcery slapt-src

[laprjns]

Can anyone tell me why entering 'chemtool.SlackBuild' in the Terminal will result in an attempted compile while I'm logged in as user, but gives me 'Command Not Found' when logged in as root?

When a command is typed into the terminal, the shell interpreter (in this case bash) searches for the command in the User's PATH. If the command is found then it is executed. If not found then the interpreter returns the Command Not Found error. A normal user PATH variable includes the current directory where as root's PATH variable does not. So when you type in chemtool.Slackabuild (which is an executable file, i.e a command) into the terminal as a normal user the interpret finds the "command" in the current directory ane executes it. Type it in as root and the command is not found resulting in the "Command not found" error. To execute the command as root you need to provide the complete path to the command so that the interpreter can find it and execute it, such as:

Code: Select all

root[chemtool]# /home/rich/test/chemtool/chemtool.SlackBuild

I'm Really not understanding this whole slackware thing

This is a Linux thing, not slackware.

[gapan]

To execute the command as root you need to provide the complete path to the command so that the interpreter can find it and execute it, such as:

Code: Select all

root[chemtool]# /home/rich/test/chemtool/chemtool.SlackBuild

Or, tell the shell to execute it from the current directory:

Code: Select all

root[chemtool]# ./chemtool.SlackBuild