SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware seems to have many tools for each task. With package management, there is pkgtool, command line scripts (installpkg, etc.), and slackpkg. There are many window managers, such as fluxbox, twm, blackbox, xfce and kde, and there are multiple applications for tasks like web browsing and email.
Why? Why is all of this included in the default install? Part of the reason texlive cannot replace tetex in the stock Slackware is size constraints. Removing some of this excess software would ameliorate that.
I am just wondering why there are so many options included in the default install when it would save plenty of space for Pat to pick one solution for each task and keep the rest in extra/. I personally do not use any of the provided window managers (except KDE occasionally); I go on slackbuilds.org and get XMonad. I do the same with my web browser, image viewer, and some other software. This is not a problem for me, but I'm still left with gigabytes of excess software. I could remove it, but with Slackware I like to have a full install, so I never run into problems with dependencies or lack a certain feature that is standard in Slackware. I trust the Slackware team's choice and organization of software for each release, so I try to follow recommendations whenever possible.
But why is all of this redundant software included?
I could remove it, but with Slackware I like to have a full install, so I never run into problems with dependencies or lack a certain feature that is standard in Slackware.
Err ... most probably they are still there and still maintained because people out there using it. Slackware is the oldest & most stable distro out there. Stable also means 'old' in many regards. And about browser, when last 13.1 was released, it had all latest. I just don't get you regarding that matter.
Last edited by jedi_sith_fears; 07-13-2010 at 02:19 PM.
The space taken up by the window managers and package managers (except maybe KDE) do not come close to the space taken up by TexLive
Moving packages to /extra will not affect the space taken up by the distribution, as /extra is included on the installation DVD
Putting stuff in /extra prevents it from being installed during a full install unless the user decides to manually use those packages later.
I'm not really concerned about texlive or space on the disk. I don't mind getting that from Robby or SBo. I was just curious about why we have KDE AND XFCE AND fluxbox AND blackbox AND whatever else.
Personally, I have a terabyte of space so I don't mind having four or five mail programs that take up half a megabyte each. I think that if the opposite was true, that I was using a 16GB solid state drive and therefore space was an issue, I would still use Slackware. I don't mind the thought process behind installing gigabytes of stuff and then using pkgtool to remove all the ones you don't want afterwords. It really lets you get acqainted with all the packages that ARE on your system.
The Arch Linux philosophy would lead to a ruddy mess of dependency issues in Slackware since we have no dependency resolution.
Err ... most probably they are still there and still maintained because people out there using it. Slackware is the oldest & most stable distro out there. Stable also means 'old' in many regards. And about browser, when last 13.1 was released, it had all latest. I just don't get you regarding that matter.
I wasn't really talking about "old" software. I guess texmex might be right; it's all there for people to choose. I was thinking in more of a salix or ubuntu fashion of having a standardized single set of software for tasks (one program per task) and allowing users to install other stuff later.
Putting stuff in /extra prevents it from being installed during a full install unless the user decides to manually use those packages later.
Which has nothing to do with TexLive being too large to include, as TexLive is too large to include on the installation DVD.
Reading over my last reply, I realized that I should have been more clear that my second point was in response to this:
Quote:
Part of the reason texlive cannot replace tetex in the stock Slackware is size constraints. Removing some of this excess software would ameliorate that.
it would save plenty of space for Pat to pick one solution for each task and keep the rest in extra/.
Personally, I have a terabyte of space so I don't mind having four or five mail programs that take up half a megabyte each. I think that if the opposite was true, that I was using a 16GB solid state drive and therefore space was an issue, I would still use Slackware. I don't mind the thought process behind installing gigabytes of stuff and then using pkgtool to remove all the ones you don't want afterwords. It really lets you get acqainted with all the packages that ARE on your system.
The Arch Linux philosophy would lead to a ruddy mess of dependency issues in Slackware since we have no dependency resolution.
I guess I've been using Arch too much. I'm so used to only having the software I choose and use that I haven't adjusted to having some extra software yet.
The dependency thing is an important point. However, the same thing works with slackbuilds.org, where the dependencies are listed.
Each tool has special characteristics thus advantages. Some of the things mentioned do not take that much space. There are times I'll use 'pkgtool' instead of slackpkg:
DESCRIPTION
pkgtool is a menu-driven package maintenance tool provided with the Slackware Linux distribu-
tion. It allows the user to install, remove, or view software packages through an interactive
system. Pkgtool can also be used to re-run the menu-driven scripts normally executed at the
end of a Slackware installation. This is useful for doing basic reconfiguration (like changing
the mouse type).
Quote:
excerpt 'man slackpkg';
NAME
slackpkg - Automated tool for managing Slackware Linux packages
DESCRIPTION
Slackpkg is a tool for those who want to easily install or upgrade packages via the network.
With slackpkg, you can have a minimal installation of Slackware Linux and install/upgrade only
those packages you need most.
You don't need to setup NFS or make dozens of CDs for all your computers; all you need to do is
to type one command and all of the latest official Slackware packages will be at your finger-
tips.
INSTRUCTIONS
Slackpkg has many features. It can search for specific files, remove all third-party packages
in your system, install packages added to Slackware since your last update, show package
lines 1-35
Sure sometimes it's just a habit to choose one over the other. But the tools are there for my usage and to make the choice. Just one example but I do want the choice that will enhance my use of Slackware.
I think the use of '/extra' as PV & Team tend to place certain things off the distribution installation is a wise one. Independent!
Slack On!
Last edited by onebuck; 07-13-2010 at 02:27 PM.
Reason: clarify
Putting stuff in /extra prevents it from being installed during a full install unless the user decides to manually use those packages later.
I'm not really concerned about texlive or space on the disk. I don't mind getting that from Robby or SBo. I was just curious about why we have KDE AND XFCE AND fluxbox AND blackbox AND whatever else.
Simply because I use fluxbox, my brother uses blackbox, you like KDE and someone else likes XFCE. Its all about choices. If you are aware of the dependencies, you need not to install 'everything'. You can install in 'expert' and get as you like.
I wasn't really talking about "old" software. I guess texmex might be right; it's all there for people to choose. I was thinking in more of a salix or ubuntu fashion of having a standardized single set of software for tasks (one program per task) and allowing users to install other stuff later.
Brother, if you are considering one program per task, and being installed default, I strongly disagree. It hampers our freedom of choice. It also disturbs FOSS.
Simply because I use fluxbox, my brother uses blackbox, you like KDE and someone else likes XFCE. Its all about choices. If you are aware of the dependencies, you need not to install 'everything'. You can install in 'expert' and get as you like.
I see. This helps Slackware appeal to a wider audience by making it easier for someone to use what they like. It's for a greater good than myself
Brother, if you are considering one program per task, and being installed default, I strongly disagree. It hampers our freedom of choice. It also disturbs FOSS.
When you put it that way, that philosophy does seem to remind me of Windows a lot. It doesn't seem right in open source.
Also, hajatvrc's point about the space usage being negligible makes sense. I only have 80GB devoted to Slackware, but about 17% of that is used currently. This "redundancy" doesn't seem to be a problem after all.
Simply because I use fluxbox, my brother uses blackbox, you like KDE and someone else likes XFCE. Its all about choices.
More to the point: many people may be using the same computer. Don't forget that any GNU/Linux system is a multi-user system. For example, my wife and I share our main desktop computer. I'll sometimes drop into XFCE or Enlightenment just for fun, but none of that affects my wife's profile and her KDE setup.
Even cooler: I can be compiling software and doing a whole bunch of junk on the computer, and then simply switch over to an unused terminal so my wife can log in and do her work while mine continues in the background.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.