I've been using slackware for while.
So, pkgtool in slackware doesn't do dependency check.
Nor there is document available about slackware package dependency.

How do you check dependency of packages in slackware other than using ldd or you can go to the package's website, if available and if the package site provides dependency doc

These two are a way to check dependency I can think of.

Is there other ways to check slackware package dependency?
or is there dependency doc available I don't know about?

Slackbuilds from slackbuilds.org, and alienbob's precompiled txzballs all install or list the required dependencies by default. The base Slackware system comes with a huge array of development tools anyway, and additional libraries beyond that are rarely needed.

However, if you attempt to install, say Gnome stuff, you're pretty much on your own if someone hasn't packaged the whole thing.

Slackware will not install a whole entire desktop environment just because you want a 400k package that has a remote dependency somewhere.

There is no official documentation for dependencies within Slackware. The thought is, if you do a full install, all dependencies will be met. If you decide to not do a full install, it is on you to figure out what packages you need. That being said, you can generally look at either ivandi's or Salix's dependency list to get a rough idea of what is required. It isn't not documented whether these are build or runtime dependencies. However, if you go the route of installing something other than a full install, we request you mention that on any threads you create, because we've spent a lot of time diagnosing issues that could've been easily solved if we knew they weren't running a full install.

As for 3rd-party software, most will list any required and optional dependencies. Some tools allow you to build and/or install all required 3rd-party dependencies.

slapt-get and sbotools come to mind

The old way is this.

Compile the package.

Run make and make install. If there are dependencies, the make install will error out. Find the first error identifying a missing dependency.

Install the missing dependency. If that errors out, find its missing dependency (see above).

Rinse and repeat until all dependencies are met.

It can be awfully annoying, but it's a great way to learn about how Linux works.

2 members found this post helpful.

And has a tendency of making a person question what the developers were thinking, linking against anything and everything, including the particular brand of kitchen sink in their own kitchen.

Then you might find another piece of software that Just Works out of the box, and turns out to be much faster, more secure, stable, and various other good things.

to explore binary dependencies, sbbdep
https://bitbucket.org/a4z/sbbdep/

note that exploring binary dependencies is not dependency management

slackbuilds, the info files, the queue generator and/or sbotools do some kind of dependency management.

1 members found this post helpful.

I suggest you also to have a look at the evergreen ruario's article on the matter.

Reminiscent of building MPlayer in the age of 2.2.x/2.4.x kernels of the early 2000's

You can also try using gnashley's src2pkg utility which creates slackware packages from source. Another alternative in addition to frankbell's excellent suggestion.

http://distro.ibiblio.org/amigolinux/download/src2pkg/

Or you can go Old School.
then learn how to read the errors to look for what dependencies you need to install first, then just keep plugging away at it. Installing them one at a time, until you work it out. Just like using SlackBuilds, only it is from source, so your package manager will not know it is installed.

so, you could after you get it all figured out, just write a SlackBuild script, then put it to use then if all goes well submit it to the Slackware SLackBuilds ...

If you are going to take this perfectly valid approach you should keep very good notes on what you have installed because packages installed this way will not be easily removed or upgraded with pkgtool. Using a tool like src2pkg as referred to above will allow you to manage the packages with the standard tools.

Might do something like:

And get fancy with filtering out file names from that if you like.

Some cmake scripts create an install manifest by default, and some make scripts allow a "make uninstall" as well.

In general though, I'd try either a local install, or just run the thing without installing at all at first, just to avoid that headache later on.

NOTE: * managed *

Let's answer the question asked.

You can use depfinder for that, after having carefully read the README. You will find packages for depfinder in the Salix repositories usable in Slackware 14.2 for 86-64 and i486 architectures.

Alternatively, as pointed out by bassmadrigal, you will find dependency lists (mostly written using depfinder) in this Salix repository for Slackware 14.2.

If you install a full Slackware distribution (which is recommended) you do not need any dependency information for the included packages as Patrick Volkerding takes care that you do not miss anything.

This is different for Slackware derivatives like Salix, because they do not ship all Slackware packages, thus they need to know which Slackware packages they should include in each Salix edition to make sure all software they provide run.

This is the reason why they mirror Slackware and add the .deps files.

2 members found this post helpful.