You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

... 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.

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.

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

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.

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 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.

...
But short of including all Slackware packages in the template that of course would need a dependency check.
...

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.