Hi, I've just built digikam from Slackbuilds.org; this is the second time I've done it, previously the slackbuilds were from slackit.wordpress.org. I'm a little confused because I've followed the directions:

unpack the Slackbuild files
download the source
run the Slackbuild script
installpkg ...

and I don't have an executable (I enter the command => nothing, I search whereis and which => nothing, I use updatedb;slocate => nothing). Is there something more I should do?

Running Slackware 11 with a 2.6.17.13 kernel.

Thanks, Joel

Did you run the script as root as you are supposed to?

Another thing you can do after making your package (as Slackbuilds' script's leave them in "/tmp") is that you can use 'ark' or the tar command to extract your package and see what is inside and if your package did "in fact" build or not. Remember a 'tgz' package is a gzipped tar archive. In there you should go to the /opt/kde/ folder and hunt for the binary in there to see if it was made or not for you. You could use pkgtool view also, but it's simpler IMO to just extract & examine the package.

Tho, you did not mention if you had successfully download, built and installed the dependencies for digikam, which are many and they do have a particular order.

Hope that helps a little

--edited for clarity I had a moment on initial post

Your explanation as to what you actually did is a little sparse. I will explain what I do and hopefully this will fill in any gaps there may be in your process.

Download the SlackBuild tarball. This only contains the script and associated files.
Untar the SlackBuild. This creates a directory containing the script, README, slack-desc etc.
I put this directory in /home/steve/Builds.
Download the source tarball. Be certain it's the same version as described in the SlackBuild.
Put the source tarball in the slackbuild directory. Don't untar it.
CD into the slackbuild directory.
su to root.
run ./foo.SlackBuild

At this point, the output of ./configure and make will fill your screen for awhile.

When the package is complete (assuming no errors of course) the package foo-1.23.4-i486-1_SBo.tgz will be in /tmp and will be owned by root. At this point, you can install it using "installpkg" or "upgradepkg" or "upgradepkg --install-new" or "pkgtoool" - whatever is appropriate given your situation.

Please note that some packages - digikam is one - require a number of other packages to work. In some cases the package won't build without these installed first. In other's, the package will build but will not run. Digikam requires a number of packages that are not included in the base slackware install. These will need to be built and installed as well. Read the info on the Digikam website. It's spelled out pretty well.

HTH

I realize I repeated much of Old_Fogie's advice (sorry), but there were some potential gaps depending on your level of experience. Easier to try to cover everything than ask 20 questions.
Anyway, I needed something to do while I waited for my coffee.

I had forgotten that if you don't install all of the dependencies that the digiKam SlackBuild could continue on (depending on which dependencies are missing) and 'look' like its created a package when in fact it hasn't created a complete package. What ends up happening is that you get a package that only has the docs in it (IIRC). I will tweak the script for the next version of digiKam (non beta's) so that if something is missing it will error out.

In the mean time, the best thing to do is double check you have all the needed dependencies installed (all available from SlackBuilds.org): exiv2, jasper, libgphoto2, libkexiv2, libkipi, and sqlite3. Then try building digiKam again. I know there are updates to several of the dependencies and digiKam itself has started a new release cycle but I recommend building with the versions that are on SlackBuilds.org. I have encountered some build problems with the latest dependencies and hope that these will be worked out by the time digiKam releases its next version.

Once you have installed digiKam you might be interested in the plugins available, digikamimageplugins and kipi-plugins. They add quite a bit of functionality to digiKam. digikamimageplugins just requires digiKam to build. kipi-plugins only requires imlib2 since the rest of its dependencies are already installed when you install digiKam. These are also available on SlackBuilds.org.

MagicMan

Hello All,

Thanks for the helpful replies; my post was in desperation at midnight. Not really desperate, just confused

I did everything exactly as you have all suggested; the only thing that I see that would explain this is MagicMan's note about dependencies. I did install all the dependencies, however I think the package for libgphoto2 went into a different directory than digikam's ./configure expected, since it was unable to find it when I manually ran ./configure from the most recent release of digikam.

After re-installing libgphoto2 and gphoto2 from source (and everything else from SlackBuilds.org or AlienBob), I installed digikam and digikamimageplugins from source. It works now. The only thing I would have done differently is that I would have built it as a package so I could track it with the package tools. I'm a little inexperienced at building packages, so I would rather just get on with it (the extended family is begging me for pictures of our son who just turned 1).

Thanks again,
Joel

Read again:

@trashbird1240

I'm glad you got it working, however, gphoto2 is no longer a dependency of digiKam. There is no need to install it unless you plan on accessing your camera from a terminal or CLI.

FYI, if you installed the lastest version of digiKam (0.9.2-beta1), which is what I gathered from your last post, be aware that they have added at least one new dependency that I'm aware of, libkdcraw. You might be able to build digiKam without it but if you use .raw images digiKam may not access them correctly.

MagicMan

I believe the order goes like this:

Digikam (0.9.0):

Requires: imlib2 (1.3.0), libkipi (0.1.5), SQLITE (3.3.12), libgphoto2 (2.3.1)

Compile digikiam (0.9.0) with imlib2 (1.3.0), libkipi (0.1.5), SQLITE (3.3.23), libgphoto2 (2.3.1), gphoto2 (2.3.1) and exiv2 (0.12) installed.

Basically the install order from scratch for digikam is like this:

1. sqlite
2. libgphoto2
3. gphoto2
4. libkipi
5. exiv2
6. imlib2
7. digikam
8. digikam plugins
9. kipi plugins

All of the above have good buildscripts at Slackbuilds.org site.

Read again:
????

Joel

MagicMan, I installed 0.9.1, the latest stable version.

Thanks everybody for all your help

Joel

Use checkinstall and you'll get a package. What I wanted to say is that you get packages when you use slackbuilds. For sources use checkinstall or magic package maker.

OKay, thanks for letting me know about checkinstall.

My main problem was that the packages I was getting from the Slackbuilds were no good

Joel

Sorry to hear that. They work fine here. However, I'm still glad you got it working so you don't keep your family waiting for baby pictures

MagicMan

I know how it's important for casual users to get what they want quickly. There were some cases when I wasn't able to solve the problem immediately (mostly due to faulty proprietary drivers) and comments such as: "what a sh*t system you have installed here, i always knew that windows are the best, i told you that linux sucks, we should have bought windows, but wait... my friend could give me windows vista for free ... " are very irritating and such comments discourage newbies to thoroughly learn linux. They drop linux because their super new video cards do not work or "I need to play wow (my all friends play)" without having heard about wine.

I believe, if we could optimize our computers to work at such speed playing games or doing 3d work, that it could blow ms windows away, it would attract more gamers, consequently more game devs, where more devs would mean even faster progression towards freedom domination. Posting a screenshot showing Doom 3 at 100 fps in high quality will attract more users that saying our kernel supports 128 processor systems and disk mounts accross the world.

I hear it all the time: as soon as something fails, it's the Linux that did it. The best example is doing videoconferencing with my family. They bought us a webcam and it worked fine on Windows for us because both parties were using MSN Messenger. However, now we have some problems to work through. Before it wouldn't work at all and they said immediately "oh, you better switch back to Windows." They didn't get that there's a lot more to our computer use than using the webcam; besides that the problem is the protocol used by MSN! (btw does Ekiga work for this? anything better than Kopete?)

There are some deep issues there about how people solve problems; I treat a computer like my friend Ted treats a car -- if there's a problem DO SOMETHING ABOUT IT. Most people just treat it as a black box because that's what it is with Windows. With Linux, on the other hand, you are entitled to do something about it, even to the level of contributing to the kernel

They also didn't get that with Windows our computer performed like a piece of crap, and with Linux it performs like a computer.

Joel