Hello from Australia,

I have been using gnu-linux for a few years - ubuntu, then wolvix as a workstation etc.
I recently changed to slackeare12.2 as my workstation and have learnt far more in the last 2 months than the previous 2 years. I have now loaded slackware64-current also for educational purposes.

To load extra applications I have been downloading .tgz binaries and used installpkg and this has worked great on 12.2 stable as if you need a dependency you are told in the terminal. However in slackware64, it tells me the package is not found (orphan pkgs load fine).
My question is, how can I can tell what the dependencies are needed by my system?
Can I type a command to ask what is required for the particular package?

I am not sure if I am ready to learn compiling from tar.g, however I do prefer to stick with the slackpkg system instead of a Gui.

Not in answer to #31, but rather continuing the discussion previous. I, at least for my purposes neither have need nor want for an automated "apt-get" functionality in Slackware. Before coming over to this distro I was strictly a Debian based devotee...for good reason. However the freedom of the Slackware package management system (the individual coupled with "slackpkg" for official programs or "sbopkg" for SlackBuilds ) in addition to the fact that the full install gives one everything but the kitchen sink takes care of many average users needs. Again, some might require more...but for me, I've finally reached Linux nirvana

@vigi - you are running a rolling development release there so any packages apart from the ones in the current tree are deemed to change and loose dependencies. You really should only run packages from the current tree with current. If you wish to run something additional you will have to build it yourself from source. Even then - as the outside libraries change - you will have to rebuild it !

Honestly - current isn't like stable and different rules apply !
Nope - however packages in the current tree will be updated in sync so will be OK. However, as mentioned, external packages may need rebuilding.
Again - you will have to get used to building your own packages if you want to run external packages with current.

thank you dgetty,

I have tried so many distros from ubuntu to the bsds, and I have found myself progressively going to the original systems after getting tired of the fluffy Gui's hiding important information. I am very happy with slackware12.2 as my workstation, so I will continue and see if I can build packages for it initially.

Personnaly, i've given up on automatic dependencies management the day that, after installing a small, KDE-based debian and wanting to install Cups to print easily, apt-get downloaded me the full Gnome install just because there was a small dependency of the Cups package on gnome-print.
That and the amount of dependencies-managing systems I borked.
And with the fact I like to compile my own stuff and this is definitely not good with a dependecies-managed package system.
With Slack, I just make a full install which is still light compared to other distros, and then compile what I need.
And upgrades work so well I have not reinstalled my systems for 5 years, moving from a version to another, then running definitely current, until my disk failed. :-)
Slack is just exactly what I want as it is.

Look at this one:
http://www.linuxquestions.org/blog/g...lackware-1990/

You can read my full thanks at the link above.

Shingoshi

Thank you very much-I will try this script.

I also do not want an auto slaptget or gsplapt system,that forever updates and sometimes creates problems.
What I want in a system is a fully functional stable base distro (preferable without the annoying extras in KDE), that can be customized to my taste with some select applications manually.

This way when it breaks, I know who to blame (me).

The way I understand slackware (please correct me if I am wrong) I can keep the original system up to date with <slackpkg> from a mirror, and anything I install manually with <installpkg> is held separately.

I believe I have found the right distro (like Buddha after searching everywhere else it was under my nose) in slackware. Each distro I have tried appears to build a glossy front and add a package manager to make life a little easier-however more often than not the gui,s do not work until you have configured the system.

I am now much preferring to learn to do things manually through the terminal, as when it does not work it generally gives you feedback to solve the problem.

thanks again for the help.

Well said - spoken like a true Slacker

The best dependency tracking mechanism is you - check documentation and observe when building. Beware of automated tools - they can fail. A good root round this forum will give you more information.
That's about it. However for this to be in effect - (the installpkg part) - you obviously have to become familiar with creating packages and not just "./configure;./make;./make install". This is itself is a very good habit to keep things manageable. Slackpkg, slackbuilds and Sbopkg all help with system administration.

Good Luck in future !

Slackware "just works" while many others "only just work".