Well, this time it has to be with installing packages:

I know how to install packages from slackbuild.org (I guess). I download the Slack Build and the source and I install the package. I've installed many things this way

What are the steps to follow to install from Slacky.eu? When choosing the package you want, I choose the package to download and then a window opens with a directory tree where files are saved. Do I have to download just the .tgz file? I've tried this with abiword but it didn't work. I know I am doing something wrong because the installation took too short. Do I have to download the source too as in slackbuilds?

How do I installed packages with slapt-get and swaret? Do I have to download source code?

How do you install most of your packages? For instance and to make it clearer, let me know how you would install, let's say, Inkscape in Slackware 12.1.

Thanks, thanks and thanks!

Glore2002.-

In this case, download inkscape-0.46-i486-2sl.tgz to a space on your hard drive. Use su to become root and run "installpkg inkscape-0.46-i486-2sl.tgz" and the program will install and be ready for use. As with all installs on Slackware, check that you have met the dependencies first.

Well if you want to install Inkscape from Slack.eu just download the .tgz package and install it:

# installpkg packagename.tgz

http://repository.slacky.eu/slackwar...inkscape/0.46/

I suggest that you read the manual:

http://www.slackbook.org/html/packag...utilities.html

I hope this helps:-)

You are right XavierP. I should check dependencies first. Coming from Ubuntu, sometimes I don't care about these dependencies. I will try again now!

Thank you !
Glore2002.-

slacky.eu's repository contains both prebuilt packages and SlackBuilds together with the app's sources. You have two options if you want to install an app from slacky.eu. You can either download the prebuilt .tgz package and install it directly, as XavierP said, or you can download the SlackBuild and the source and compile the application (which will create a .tgz package for you which will be identical to the prebuilt package unless you change some options in the SlackBuild). In the inkscape example, the prebuilt package is located in the top-level inkscape directory (inkscape-0.46-i486-2sl.tgz) -- you can just download that and install it using installpkg. If you want to build the package using the SlackBuild, ignore the prebuilt package and navigate to the src directory, which contains the SlackBuild, the slack-desc file, the app's sources, and any other files required for the SlackBuild to function (including patches, etc.). If you want to use the SlackBuild, download everything in the src directory, make the SlackBuild script executable (`chmod +x appname.SlackBuild` should do it) and run the SlackBuild (./appname.SlackBuild). Note that slacky.eu's SlackBuilds follow a different convention than slackbuilds.org -- packages are usually built in /tmp/tgz and the final package is left in the current directory with the SlackBuild instead of in /tmp.

Generally I would recommend you see if there are SlackBuilds before installing binaries from package repositories such as Slack.eu. The SlackBuilds READMEs (at least from SBo) will always give you a heads up on what dependencies you need and these are generally included on SlackBuilds.org as well.

I also recommend you read some of the slackBuild scripts so you can learn how to make your own scripts. There are some HowTos on the SBo site as well.

I agree with the above in that I prefer to run my own SlackBuilds rather than downloading pre-compiled packages, but the above implies that Slacky.eu does not list dependencies, which it does. I have recently installed a couple of packages from them & had no problems with dependencies as all were listed; one even had a .tar.gz in the same directory as the .tgz file with all the dependencies in it.
Regards,
Bill

Regardless of whether or not a package or build script site lists the dependencies or the upstream sources lists them, you are always more likely to have a better working package if you build it for your system. When you do build packages for your system, it is nice to have a build script REAME which lists the dependencies, and it is also nice for the dependencies to be available on site as well.

All dependencies for slacky.eu are located in the src/ directory for the app in the slack-required file. I think all of the dependencies are available from slacky.eu as well. slackbuilds.org should not be leveraged above slacky.eu in this respect, in my opinion. I trust slackbuilds.org more because I know more about it and because I know some major Slackware contributors run/contribute to the site, but slacky.eu has everything that slackbuilds.org has in terms of functionality (and more, since it includes prebuilt packages). I too have a preference for slackbuilds.org, but groundless negativity towards the site isn't really helpful. slacky.eu is a great resource containing SlackBuilds, dependencies, sources, the works.

I think you are misunderstanding me. I never meant to imply that there is anything wrong with slacky.eu or that is it not as good as SBo. I was simply saying that it is generally preferably to build your own packages versus using someone else's binaries. I said it was also nice for sites to list (and possibly obtain/build) dependencies, which both SBo and slacky.eu do.