Because he said that does not know the relationships between packages. If he does not know why was added a package, then who?

And it is not a question, but a statement.

... Making sure it is self contained, in other words that running any of the included apps won't fail by lack of a dependency. That is the point. But short of including all Slackware packages in the template that of course would need a dependency check. Let's take a simple example: you are not going to include dbus in a KDE group, are you?
But then if you remove dbus, will KDE work?

In other words, only Slackware is guaranteed to be self contained, none of its sub sets.

BUT, the XFCE would work without DBUS? Maybe you want just to use that XFCE? :D

And that's very bad in the day when Slackware will ship Plasma, and you will want badly to continue to use KDE4. ;)

Where did I say anything of the sort? I said that we don't have a magic list of dependencies that we're keeping secret for some reason.

Only Bob has that list. ;)

Lets keep all the gods out of a discussion about some trivial text files. ;)

Darth, I think you are misunderstanding EH and PV...They merely said Slackware will not do this, they never said you or someone else cannot do it. They even suggested (with a tip of the hat or a smirk) that you could provide this service to the community. Didier showed you how it is already handled by Salix repo using slapt-get...So it seems like this debate is going to become the sound of one hand clapping soon.

You keep implying that it would be trivial ("a low burden of its adding") to add and maintain a new file in EVERY SINGLE PACKAGE in the distribution. That is, if I even thought it was a good idea.

Slackware is not required to conform to your specific needs/wants. You are free to suggest changes, additions. The maintainer is the one who makes the final call on the package sets/configuration of Slackware.
As PV and EH stated you are free to modify Slackware to your specific use case. I'm not sure why you feel the need to be abrasive; that is not helpful on our forum. Have a nice day. :)

You are right, I can do that myself, and I can even provide myself those information in a bright day.

BUT, to be of general usefulness, those information should be included in distribution, to spread to users, included in the packages.

Unless that, will be my individual work, and for my own wellness.

Thanks you, I think that I handle well this task for myself, but I thought for an improvement. Useful for many.

Will that be adopted, or not? Only Patrick would decide, I for one I showed arguments for my POV.

Please do not put words in my mouth.

I do not say that maintaining of this information, then of those files, is a trivial task. Your time and work is invaluable.

But, I tend to consider the gods, all of them, as important entities, which have more important things to do than to look to merely things, like even this discussion.

Or, how its said in my very own Christian Orthodox religion: "Do not take God's name in vain"

This is the third commandment.

It is a common mistake to think that dependency resolution will automagically solve the problem with the full install. Slackware does not split packages. For example if you use slapt-get to install wpa_supplicant on a minimal system, it will pull everything and the kitchen sink. Wpa gui depends on QT, QT depend on gcc gcc-c++ Xlibs and mesa, mesa pulls llvm and so on, you get the picture.


Cheers

Don't say them then.

William Shakespeare used for doing his writings a trivial material: paper

But his geniality and efforts made us to know him after hundreds of years.

I think is a big difference between the materials used and the work made. The materials could be trivial, while the work could be genial.

I do not think that someone would not be considerate for the work made, just because it is on some "trivial" text files, so maybe that issue is seen bigger than it is.

Of course, not the used materials matter, but the inspiration, geniality and the work made, which create the value of the opera.

I think that everyone, including myself, have all consideration for the Patrick Volkerding's work and his time spent to build Slackware.

That's WHY we are here, after all. Because we appreciate his work.

But looks like he's a bit grumpy today... ;)