Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 06-01-2014, 07:13 PM   #1
Registered: May 2014
Posts: 209

Rep: Reputation: 0
A question about software and SlackBuilds

I tried to install openbox by running slackpkg install openbox, which I knew would not work. I went to SlackBuilds and in the Howto it says to download the archive and also the source code for the install. Now, what if I download a tarbell which does not have source like steam? Would I still be able to install it?
Old 06-01-2014, 07:24 PM   #2
Senior Member
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,646

Rep: Reputation: 958Reputation: 958Reputation: 958Reputation: 958Reputation: 958Reputation: 958Reputation: 958Reputation: 958
you can always download binary package (and source) from AlienBOB's repository:
Old 06-01-2014, 07:33 PM   #3
Senior Member
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
Alien bob normally puts a "dependencies" txt file in the package directory. Just pull the whole directly down to your hard drive and take a moment to read it, it will save you a lot of trouble.
Slackbuilds lists dependencies on the page where you pull down the packages. Similarly, make sure you've got what you need to install the pkg before you try to install it and with Slackbuilds be careful you're downloading the right binaries (32 vs 64 bit) Alien splits the directories so it's hard to make that mistake
Openbox will work like a charm if you read and follow the directions carefully.

Last edited by dijetlo; 06-01-2014 at 07:41 PM.
Old 06-01-2014, 07:51 PM   #4
Senior Member
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
Sorry, let me answer your question.

Would I still be able to install it?
Download all the files in the directory containing your package.
Do an md5sum check to make sure you have the uncorrupted source in a tarball. If you need help with that, post back
Go to a terminal, go to that directory and use a user who can "sudo" to root permissions, preface each of these commands with "sudo".
"tar xvf" <sudo tar xvf>the file with only the package name and not the version number, it will create a directory beneath it. For example "openbox.tar.gz" will create a directory called "openbox". Move all the files related to openbox into that directory and then CD into it.
Read all READMEs' and text files. If you have a question about what you're reading, ask.
Look for a file named "openbox.Slackbuild". It will be in the directory you downloaded and moved.
You have to change the permissions on that file so
"sudo chmod 770 openbox.Slackbuild"
Then you just type "sudo ./configure openbox.Slackbuild" and it will build your package. The build can be a little intimidating when you first start doing this, eventually it will make you sleepy watching it.
When it's done it will tell you it copied the installable package into /tmp/sBO/<packagename>".
"installpkg /tmp/sBO/<packagname>" and you watch the script run until it pops out with "package "packagename" installed."
You don't have to type "ldconfig" at the end but it's kind of like throwing salt over your shoulder.
You should be golden.
Aliens install basically the same way. except he has the source built if you just want the defaults. Just download everything and follow the steps up to "./configure". With aliens stuff you just move it to /tmp and type "sudo installpkg packagename" and it will install
I'd pick a night I had some time and a package that I didn't care much about and practice with it. It sounds harder than it is, after you've done a couple it will be second nature to you. Almost everyone who has "Slackware" under their name can help you with this so you can always get a relatively quick answer from here.
The advantage to this system over the automated one is you'll notice as you get better at this that you can control a lot of the functionality of the packages with switches you insert when you configure them. You get a much better level of control over what you're installing and how it's going to work than when you use an automated package handler.

Last edited by dijetlo; 06-01-2014 at 08:11 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Question about skiabox Slackware 4 11-14-2012 01:16 AM
Installation of software on Slackware - is there any other way exept slackbuilds? firekage Slackware 49 01-05-2012 08:41 AM
slackbuilds 64 bit question charlie_lab Slackware 7 08-29-2009 05:04 AM
SlackBuilds and Software Versions LoneStar Slackware 6 06-20-2009 01:44 AM
Slackbuilds question svar Slackware 3 01-05-2008 01:36 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:45 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration