keeping slackware uptodate/ package management

[portia]

installpkg, pkgtool or even kde package manager can indeed install with return -0 but later you wonder why the app does not run when activated.

So how am I supposed to know what's needed for it to run. It's easy when it gives errors during installation, eg. qt4 is missing, etc. However, when it installes without errors, how can I find it out what dependency to satisfy?

thanks

[dijetlo]

Hand compile apps that don't come in the distro.
./Configure-> make ->make install
There are almost always instructions in the package, if not you can pull out the config file the installpkg tool uses from the tar ball and edit it.
Most stuff goes in without a problem, I use installpkg more often than I probably should. Even if it exits with a 0, run the new app and make sure it works. If it fails, back it out and hand install it, you'll almost always find the problem is in ./configure

[portia]

Ok, that makes sense. thanks

[winlia520]

Hi,
I'm new to slackware 12.2 and am slightly confused with its package management.

As far as I know there are 2 sources of packages.
1. The repository from the official slackware website
2. Alien bob's slackbuilds


I've got a few questions. Is it ok to mix packages from both sources?
How to best keep everything up to date. Is sbo_pkg enough for package management?
Sbo_pkg draws on sources from the official slack website, am I right? So what about keeping
slackbuilds up to date?



thanks for your replies

yeah! very good ! thank you I learn about!