Hello. I know that it is quite usual question but I still don't understand this.
Lets take xfce for example: it breaks if you delete thunar from it. But it is problem of xfce architecture, isn't it? So if you install package and its developer provided requirements list with, in what circumstances I don't want to install them. Why on earth do I need broken package? Moreover to achieve stability we need to install 15GB of packages or otherwise we risk to brake build of some sbo packages. And at the end of the day, I suppose, vast majority of users (?) use sboinstall anyway. Can someone explain me this, please? Don't hate me, I just don't get it.

Simplest answer is that it is just the philosophy of Slackware.
https://docs.slackware.com/slackwarehilosophy

3 members found this post helpful.

The full post:
https://www.linuxquestions.org/quest...ml#post4739581

8 members found this post helpful.

So there is no particular reason. I am asking this because I came across the statement that there is no DH in slack because "we don't need it". So this guy who said it is not right, I suppose. Right?

The reason is Slackware.

1 members found this post helpful.

AFAIK, weren't there people working on tools to do dependency checking? I seem to recall it being bandied about for slackpkg+?

The philosophy IS a particular reason, probably the most important

There is a dependency resolution in Slackware, made by Patrick Volkerding himself.
Therefore, the package manager does not need it.

For 3rd party repositories, as garpu said, some tools provide DR, like slpkg or slapt-get

What is it?

What "What is it" ?

Dependency resolution instrument that you just mentioned

Is there a particular reason you'd want to remove Thunar if you're planning to use Xfce?

Actually, yes, perhaps there is. Maybe you suspect that there's a bug fixed that's a problem for you, or there's a feature added that you're interested in that's in a newer development version of Thunar that's not in Slackware -current. So you'd like to remove Thunar without having the package management system decide to remove the rest of Xfce for you. I guess with some other system you could remove a package with the --nodeps option but then you'll have any future package installs/removals calculating dependencies with incomplete or inaccurate information.

You could try using slapt-get, I guess. Best of luck.

13 members found this post helpful.

It's really not hard to do the checking one's self. Official packages and Alien Bob's repositories assume you're doing a fully-patched, full install. If Alien Bob has other dependencies, he'll say so. Slackbuilds will list any dependencies either in the page for it, or in the .info file of the slackbuild.

Ahh, thank you, but that was just an example from my past experience. Thunar could not open for me on my previous install about a year ago and I just wanted to delete it just for sake of prettiness because I wanted so.

I probably expressed myself badly
The dependency resolution IS actually made by Patrick, upstream (I don't know how). Not by a user tool
All you have to do, is to install the whole thing

If you remove something, don't blame anybody else but you

side note:
Third party repositories assume that EVERYTHING is installed from the official repository, and do not list the official Slackware packages as dependencies.

1 members found this post helpful.

It is a good idea if you're new to Slackware to do a full install because then everything works out of the box with all dependencies met. As a general rule here on LQ we prefer to provide tech support for full installations of Slackware.
Dependency resolution distros are a fine thing when they work properly . It has been my experience that dependency resolution package managers can and will break. The lack of dependency resolution is a feature not a deficit.

7 members found this post helpful.