Unless if you are installing Slackware on a laptop with SSD, then you'll need to be a bit more careful on how you utilise the limited resources.

By the way, I installed Slackware on a Zenbook UX305 with 256GB SSD. Installed everything else except XFCE set and I think I removed a few other packages later on like blackbox, fluxbox and window manager. I use KDE as my main DE and haven't encountered any problem with the system except for the bugs in KDE itself.

In my opinion, xap, kde and xfce sets are like the 'outer shell' of the system consisting of mainly graphical tools. kde and xfce need to be installed as a whole, but packages in xap are safe to remove individually.

When you're first getting your feet wet, actually go "whole hog" as others advised. Discover what's actually there before you start removing stuff.

But it doesn't have to be a permanent decision. On my systems, I inevitably chucked all KDE/KDEI packages sets, putting both in /etc/slackpkg/blacklist so I wouldn't inadvertently get the new packages added to these sets later. Using slackpkg or removepkg, you can also chuck the others WMs you don't want--I left only Xfce and twm, and I've yet to suffer any repercussions while following -current (apart from the use of software based on KDE libraries, which is no problem for me at this time). Your results may, of course, vary . . .

1 members found this post helpful.

I do a full install with the exception of the E directory (Emacs), and Mozilla Thunderbird. I don't need Thunderbird because I use SeaMonkey mail. If you're not going to be compiling a kernel, you might also want to skip the k directory. I also don't install the kdei directory, but kdei is unchecked by default.

1 members found this post helpful.

It will only resolve dependencies if the repository supports dependency resolution.
So if you replace the host in slapt-getrc marked 'official' with a regular slackware directory, it will still work but won't resolve nothing.
Wouldn't recommend it if you're not comfortable resolving it all manually, just saying it works fine either way.

I usually skip installation of the E, KDE, KDEI and Y series completely. From the XAP series I deselect whatever I do not need. I use XFCE.

Slackware is a complete operating system.

While you can remove parts, it is generally not recommended to do so as various packages can have dependencies between others, even those you might not think so.

Just do a full complete installation, and don't use the other DM/DE/WM packages.

Unfortunately not everyone has deep pockets or even enough to upgrade very easily without hurting somewhere else for it (should I get that tire the bike needs or go another month and hope for the best? etc), nor does everyone have some kind of brick and mortar computer parts store they can hop in the soccer mom vehicle and drive a mile to and walk out with whatever it was they wanted (for example, with my disability being crushed discs and unreparable torn muscles and tendons in my back, the only vehicle I own is my motorcycle. Bundling up just for a short ride in 23 degree (farenheit) cold just for something you make sound like it's nothing - it really isn't that easy or fun). I understand what you're saying, but those with the ability often never seem to think that they really aren't such a big majority of those that *do* have that ability to just get something and it be as trivial as you make it sound. Not meaning for this to sound harsh on you or anything, just letting you and others know that this situation for *many* people *is* there.

I'm in full agreement though with you that a full installation is just plain simpler and takes care of so much of having to hunt down and build dependencies (not that it's hard to do with Slackware...at least I personally don't think so) and such. After all, if someone's really got such a small hdd that fitting 4GB on it might be too much, it's so old that I'd worry about using it much longer anyway and I'd make it a priority to save up for however long it takes to get something newer, heh heh.

MHO in itallics.

1 members found this post helpful.

I really dislike the argument that hardware is cheap nowadays. Want to save disk space? Just buy another hard drive. Software too resource consuming? Buy more RAM, it's cheap. Computer slows down? Upgrade your CPU. Video performance decreases? Buy a new graphics card.

Not everyone finds it amusing to go buy hardware or assemble their computer. May be some users just want to squeeze as much as possible from their current hardware, without the need to buy new parts. Instead of repeating that 'Slackware is meant to be a complete install' why don't you give a suggestion of what to do in order to trim it down a little?

I, for example, do not use KDE at all and I do not want to have a bunch of KDE applications that I will never use just laying around. I know they would not slow down the performance, it is just a personal preference to keep mainly software I need. That and the fact that I have a 60GB SSD.

1 members found this post helpful.

I don't think the argument is so much that "hardware is so cheap just buy some more" as "storage is so capacious and CPUs so fast on cheap machines". If your machine has a 40GB hard drive then, really, a full Slackware install isn't going to make much difference over a slimmer one unless for some reason you're trying to cram a load of movies and the like onto that ageing hard drive also.
Of course, as alluded to in FTIO's post hardware so old the storage and CPU aren't up to Slackware is likely so old that it should be expected it will fail any second now (I am going further than FTIO, I know).

Of course, yes, there are exceptions and it's good to use things until they are beyond economical repair. But I don't think that anyone is really arguing against that. Just pointing out that if not precisely now then at some point in the not too distant future the vast majority of machines still working will be able to fit a full Slackware install and more onto their storage with no problems. So, if you have one of those machines it seems silly not to install everything just to save space you have plenty of.

I love what you posted. I'm not going to buy a new TV, just because I don't have a smart one. Goes for computers, hardware, microwave etc... Some people can't grasp the concept, not everyone wants unnecessary files, resources on their computer. Some people like simplicity. If you speak spanish, you're not going to have every language pack installed. Even if one was bilingual. Why use that space for apps you don't use, when it can be use for things like storing pics, movies or whatever reason.

The space saved is entirely insignificant unless you go the full distance and either reduce your system's functionality greatly or greatly rethink what packages you have installed and recompile/remove large portions of your system. Just removing the desktop managers and window managers expecting to save much useful space is silly.

I'm not saying someone shouldn't do this, just don't delude yourself as to why it would be useful. The biggest benefits would be learning how your system works and how to maintain it better. Space saved is somewhere towards the bottom of the list.

3 members found this post helpful.

I have done full installs minus KDE in the past (just using XFCE) and then find that I need a KDE application such as kdenlive or ocular, so now I just do the full install.

The problem with this (IMHO) is that the menu is now full of dozens of KDE apps. My answer to this is to use Fluxbox and build my own menu tree - very easy in Fluxbox. Then if I find that I need a KDE application - I just add it to the menu! My GUI is simple with very few things in the menu, but I have the full Slackware hidden in the background.

My two cents...

1 members found this post helpful.

That is a very good point -- depending upon what type of menu[s] you use and how you use it[|them] there could be issues with too many entries. I know, though, that with XFCE one can hide menu entries so with XFCE it's OK but may take some additional work to make things neat.

Thanks 273.

You can configure menus in XFCE but I am not sure how to do this without using the graphical menu tool. Fluxbox has a simple text file with the menu structure - very Slackware-like - which you can copy as a backup before you start configuring your own.

I think this approach at least partly addresses the wishes of those Slackers who want a minimalist system, at least it gives a minimal interface.

Cheers, Bill