There is no package in slackbuilds.org, you build one yourself running the shell script (the SlackBuild). Also, this isstated in the README:

One can use SBOpkg to build external sources?

BWAHAHahahahaha! Welcome to the maze that is Slackware package management for noobs! The fun begins!

I guess I got jdk installed, but how should I use the 'profile.d'-stuff?
source it from .bashrc or .profile? Now I copied the lines from jdk.sh into .bashrc into my home directory, but what's the right way so that eclipse can find java (when I get it installed)?

kōhai turboscrew:

You are welcome. And your summary is correct.

I will return to the wifi in another post, but let me try to get you started on the slackbuilds.

Let us walk all the way through the jdk install to learn from a simple example, then we will move on to more advanced moves...

We will work with the most up to date jdk and build script, so let's get them first. First, the slackbuild - you can use the one from your install media, /extras/java/... or simply download from here (they are the same). This is the Slackbuild used by Pat before Oracle made java not redistributable, so it is as official as you can get!

You will need all the files in this directory structure, let's put them into a directory named java (in your home directory) on your local machine:

The java.SlackBuild is the main script that builds the package from the jdk or jre distribution tarball.

The slack-desc file contains a formatted text header that is written to the screen when the package is installed or queried.

The profile.d/ directory is specific to this package and contains initialization scripts that set the environment on the system the package is installed to and are included here so that they can be added to the package as a convenience. These will be installed to /etc/profile.d when the package is installed.

SBo scripts will also include a [pkgname].info file not included here. It contains source URLs, checksums, maintainer, dependency and other info.

OK, next we need the source file(s), or in this case the distribution tarball. For an SBo script you would get the URL from the pkgname.info file, but here we will just look online for the latest. I assume that you want the JDK, and probably the latest. Either of these will build, but the second is the most current - recommended:

jdk-7u60-linux-i586.tar.gz
jdk-8u5-linux-i586.tar.gz

Just in case Oracle throws any stumblingblocks in your way, you can find both from the main java download page.

Put the downloaded distribution tarball into the same directory as the java.Slackbuild then cd into that directory if not there already. It is also a good idea to verify the MD5SUM on the download, but I did not see those posted at Oracle so I'll include it from my own. SBo *.info files will contain an MD5 for the sources they use.

The script will then create a working directory /tmp/package-java and unpack the distribution file there. It will then do what it does to build the package file structure, docs, profile, etc...

When done the package will be found in the /tmp directory...

If you want to archive the package for reuse you should move it to a safe archive location, or you can simply install from /tmp if you prefer.

Done!

For your shell to pick up the java environment you will need to log out then login again (those profile.d/ scripts).

This is the essence of Slackware package management. What the Slackbuild scripts do for you is to build a well defined package from sources, either source code or pre-packaged binaries as in the jdk case.

Please note that this did NOT use sbopkg or any other tools, but uses only the native pkgtools tools, makepkg, installpkg, upgradepkg or removepkg. sbopkg is a great tool, but is an accessory, not an essential part of the process.

So learn the essentials first, then if/when you use sbopkg or other tool you will understand clearly what it is doing for you!

After you have jdk installed, we will do another example from SBo - do you have a program you need, or should I pick one of my own?

NOTE: If your /tmp directory is on disk you will want to remove the accumulated build trees/packages as they can use up a lot of space if you build many packages!

2 members found this post helpful.

For jdk you can place the source in a directory with the other files found in /extra/java from the slackware dvd. Then you run the slackbuild in the directory. You may need to edit it if the version number has changed or something like that.

You could consider if openjdk address your needs. If so it is available through alien's repositories.

Brian

I see you were installing while I was typing! See above post #64...

sbopkg only downloads and builds packages available on slackbuilds.org.
Maybe this can help.

1. For installing and keeping updated packages which are part of the standard distribution, use slackpkg (comes with the distribution).
2. For installing and keeping updated packages which are contained in a variety of high quality repositories not part of slackware itself (such as alien's repositories, slacky.eu, etc.) install the slackpkg+ add-on and continue to use slackpkg.
3. For building, installing and keeping updated packages for which slackbuilds.org maintains a slackbuild use sbopkg.
4. For all other software which you need to build yourself because it is not available from any of these sources, try src2pkg.

Brian

1 members found this post helpful.

Here is a simple activity diagram (i.e. flowchart) of the steps necessary to build and install packages using slackbuild scripts.

Attached Thumbnails

 

1 members found this post helpful.

That's what I thought. (You mean, I was actually right? I may be catching-on to this stuff, finally! )

Ah, another vote for src2pkg! Seems to be a consensus (....or is it "consensi"?)

No.s 1-4 above should be included in the official Slackware documentation. Others have made me aware of those facts, also, but at this point, the repetition helps! Those few simple lines would eliminate a lot of confusion for us noobs coming to Slackware, if we had access to that info from the beginning. (But then again, then there'd be no mystique about Slackware, and us Slackers might lose our geek-like status among the unwashed masses using lesser OS's! )

I mean, part of the fun in using Slackware is:

*:"What version of Windurs do you use?"
"Windows? Pffft! I use Linux"
*:"Oh...Ubuntu? Mint?..."
"Pffft! No, the real thing- Slackware."
*: [Stares in slack-jawed admiration]

You can of course compile from source on Slackware using make, but, I prefer installing packages that I can easily upgrade or remove. So I will install 3rd party packages from slackbuilds.org, from trusted sources like rworkman or alienBob, or build my own packages using src2pkg.
However, I find that Pat includes such a wide variety of software in a full install of Slackware that I don't need to get too many other applications from other sources.

kōhai turboscrew - welcome back!

Slackbuilds: Advanced Class - SBo Scripts with Dependencies and Other Surprises

This example will cover most of the scenarios that you will encounter when building from SBo scripts - and leave you with a terrific new program installed.

I have chosen one of my own favorite applications as an example, TaskWarrior. It is a full featured task manager for the shell.

So, having decided to build TaskWarrior we begin by finding it on SBo (click, click, search for "task"), and we arrive here.

Note what is visible in the page view on SBo - everything you need to know, become familiar with it:

For now, download the task.tar.gz file to a convenient working location or your home directory. (You may wish to verify its gpg sig, but I will skip that here).

Here we get two very important bits of info: The download URL and MD5 (same as on SBo page), and the list of required dependencies, just one - lua. So learn that you can always be confident that downloading only the SBo SlackBuild archive (***tar.gz) provides everything you will need to fetch sources and build the package.

Now lets download the source using the URL from the task.info file (or the SBo page, just wanted to show you both are available), and always verify the MD5.

Our first surprise - the source is not there! Following the link to the project home page we find that there is a newer version and they do not make previous versions easily available! Bad practice, but it happens... So lets get the latest stable version which is 2.3.0 according to their website and see if it will build...

... and we need to update the SlackBuild script to recognize this version...

OK, we are ready with the task build, but we already know it also needs lua, so lets get it - just follow the link from the task page on SBo, download the lua.tar.gz file and untar it, then start to finish...:

That wasn't so hard - you have built and installed lua! This is a typical SlackBuild session, you will be doing it in your sleep!

Now that we have lua installed, back into the task directory...

Done!

A great place to learn your new program is to look at the man pages:

But I leave that to you, and be sure to visit the project website for more info.

Now this all looks like a lot to do, but let's recap the essentials, this will be true of any SBo script, and most other slackbuilds you will encounter:

You can (and I do!) completely manage your Slackware systems using nothing but these methods and tools! I actually prefer this to any automation - I never end up in an unknown state!

But if you decide you like sbopkg, just realize that what it does is automates these same steps for you, no other magic!

Thanks for attending today's class!

Sensei astrogeek:
That's what happens when you do these things after midnight: You don't notice the name of the directory. It's PROFILE.d. How can I be that stupid...

Yes I installed jdk using the Oracle sources and the stuff from slackware.osuosl.org.
I didn't use SBo at all.

From the advanced class:
That's good to know - even if I have full install.

Very good point. I've been there in an unknown state with some installs (on Ubuntu) quite too many times. (I think that sooner or later I'll get rid of Ubuntu.)

That's why I was wondering if you could download, say, jdk in some directory and then
use sbopkg to install it. Probably I could, but at this stage of my learning process it might be a bit complicated.

BCarey:
I don't think OpenJDK can be used, because in eclipse SBo says: "This requires: jdk".
I also agree with Sumguy that your list of which tools to use in which situation should go into the documentation.

hitest:
Installed qemu 1.5 into my Ubuntu-machine using "make install". BIG mistake.
It didn't work, and I had quite a job removing it manually.

BTW, does anyone know how to force XFCE to use given keyboard map.
I rebooted my machine, and now console uses FI, but XFCE uses US.
It s hard to find the keys for special characters.
menu settings keyboard Layout doesn t seem to have any effect.
Tried to check use system defaults too but no effect.

And now all of a sudden, I keep getting popups about wicd even if I use network manager
rc.wicd has no execution rights.

Or use a text editor like nano to make that change in /etc/X11/xorg.conf.d/90-keyboard-layout.conf

For Finnish the option XkbVariant can be set to following values if need be (assuming that you use the evdev driver):Of course you'll have to restart he X server for these changes to take effect.

1 members found this post helpful.

Try this, as root (of course):
And edit this line in /etc/X11/xorg.conf.d/90-keyboard-layout.conf to what you want :
Curses!!! Beaten by a faster typer again!!!

1 members found this post helpful.