slackbuilds.org
 

I think I love slackbuilds.org.....except that I'm doing something wrong and nothing works.

The instructions on the slackbuilds.org FAQ (and the slackbuild wiki) state that after I untar some things, there will be an OUTPUT file in /tmp, and that I should then use installpkg to install the files. But doesn't installpkg ONLY install things in .tgz form? I've tried numerous slackbuilds and NONE render a .tgz file.

Seems like a simple step that I'm just not getting. Any pointers?

what are you wanting to build? i would check with the slack.build files in the source directories from an official slackware mirror too,...

never hurts to get more than one opinion when building from source...

I've tried a few things. perl XML parser ("XML:simple-2.18"), scribus, tango icon set, audacity......basically I'm just trying to learn how to install things. I guess I could try slapt-get, which I've been reading a lot about lately.

Still I'd like to be able to say that I can build from source. Just sounds like a good thing to know how to do...but maybe i'm jumping the gun.

Here are the steps to make a slackware package using a build from Slackbuilds
http://slackbuilds.org/howto/

As it says OUTPUT defaults to /tmp this is where the package will be located after is is built.
You would installpkg /tmp/<some_package>-<some_version>-<some_arch>-<some_build>_SBo.tgz
to install the package.

You are doing something wrong.

1. Download the slack.Build script for your program (someprogram) you want to install. untar the script: tar -xzvf someprogram.tar.gz
You will now have a directory called someprogram in your build directory. Download the source for someprogram. Move the source inside the some program directory. cd into that directory.
2. Inside the someprogram directory there will be a build script called someprogram.SlackBuild.
3. Become root type su, enter root password
4. Type #chmod +x someprogram.SlackBuild
5. Execute the build script by #./someprogram.SlackBuild
6. Sit back and watch as your slackware package is created.
7. cd /tmp
8. #installpkg somperogram-i486_SBo.tgz

Are you following this? http://slackbuilds.org/howto/

If not, do so, and it should work.
If so, please post complete build logs (how to get those is linked in the bug reporting page).

Wow. That was the clearest take on this that I've ever read. The Slackware Essentials book included AND the HOWTO on slackbuilds.org combined. I nominate your instructions to be a STICKY. No kidding. Surely other people have asked about this?

Anyway, it totally worked. Thank you very very much.

Cool.

Er, I see now that you already referenced the HOWTO. Hmmm...

If you're trying to build scribus, then here's your steps:
1. Download http://slackbuilds.org/slackbuilds/1...scribus.tar.gz
2. Extract the script tarball.
3. Change directory to inside the name of the app (scribus in this case).
4. Download the source code for the app. There are at least two ways to do this:
OR get the download link from the SlackBuilds.org scribus page
5. Run the SlackBuild script.
Note that you can alter the ARCH, BUILD, or TAG variables directly from the command line (without editing the script), although in the case of ARCH, you do have to pass a valid value.
Some scripts also include other variables that can be passed from the command line, and those are mentioned in the README files for those scripts. The way to do this is as follows - for example, if I want to build scribus with i686 ARCH, package BUILD number 2, and with my initials as the build TAG, I would do this:
One last point (for those who are not aware) - we have an easy method of obtaining script tarballs for things that we host. All of the tarballs are available by name from http://slackbuilds.org/ports/$SLACK_VERSION/$APP.tar.gz
For example:

EDIT (late addition):
Now after taking all this time to type this, I see that hitest has beaten me :-)

Yeah, that browser reload button just can't get hit often enough around here.

Anyway, I've copied BOTH hitest's and your responses into my personal linux notes collection, and am grateful. Thanks a lot......and now that I know how to do it - thanks a lot to everyone over at SlackBuilds.org! (most of whom are probably lurking around this forum every other day or so...)

You are welcome:-)

You are the man, Robby! Your well-organized website taught me how to install SlackBuilds. I greatly appreciate the hard work that you do for us. All Slackers owe you a lot.
Thanks, man:-)

Well, I appreciate it; really, I do. However, I think your gratitude is misplaced -- http://slackware.com/~volkerdi/ is where it should be directed :-)

Robby,

Methinks you are far too modest. I echo the comments from hitest.

Pat provides the perfectly cooked meat and potatoes, but the outer circle of yourself and Eric and others adds the garnish and gravy that make the whole Slackware dish a delight.

I, for one, would not have managed the transition from Slack 11 via current to Slack 12 without reference to your indispensable notes.

My sincere thanks to you and all others.

slackbuilds are ok, but i almost never use them, prefering to simply build from source what i want/need that is not included with Slackware, i don't do anything fancy & complicated and just use the minimum parameters needed to get a functioning software install, i always run ./configure --help first and read the README & the INSTALL files for anything important, ./configure and make will always tell you if something is wrong so you can correct any missing dependencies or parameters...

slackbuilds are great for packages that are tried & true and you know for sure the package will build as expected but when a slackbuild continues all the way through to make install regardless of errors then you may end up with broken software installed, so i rather build source the old fashioned way when it comes to adding software Pat V. has not included with Slackware...

just my $00.02

I appreciate the reply, Robby:-)
I think that The Slackware Linux Project has grown to the point that the entire Slackware Team is needed to bring each release to completion in a timely manner:-)
No argument from me, Robby:-) Patrick rules!