Slackware is best installed full.
If you are new to Slackware you better install it all the first time around.

Some of us, who know and use Slackware for a while now, might have scenarios where installing a heavily pruned system is of interest or of benefit.

So far I've read many things about TAG files but never came to use them.

In requests for current we have come to agreement to explore how useful TAG guided install would be for the day to day users of Slackware and how many users could actually benefit of such a system.

Post your TAG files here, explain what purpose you use them for and cast your vote for the opinion matching your mind the closest.

And please be polite in discussing if we would benefit from such a feature or not.

Since Slackware releases last for years, I see no good reason for me to ever install some form of limited system. I always go Full Recommended Install as it will save me time for all those years of not having to chase down dependencies and this has served me well for ~20 years. It adds up. Additionally, every now and then I will see some app I know little or nothing about and just casually launch it and see what it's all about. There is also a minor safety factor in that if some driver install or tweak borks a WM/DE (rare, but does happen) I can always find one that still works to help me suss out what I did wrong or what failed.

I don't think I can possibly express how grateful I am that Slackware exists. I spend many hours every day on my PC and repeatedly I find myself noting just how good Slackware really is... at least for me. Nothing else quite compares. It's truly in a league of it's own. I love it. It's like an old best friend.

6 members found this post helpful.

maybe some clever person will build a smart tag generator tool thing that makes it easy do sort it all out, then when you go to install slackware you can just point the installer at your custom tag file and BAM! you got your custom slackware install

http://www.slackware.com/~alien/tool...e_generator.sh from years ago.

I should mention that slackpkg knows the concept of "templates" which are functionally similar to tagfiles, but to be used at a later stage in the installation of a system.

7 members found this post helpful.

Thanks Alien_Bob, that worked good

As a web developer I prefer the full recommended install. I have done minimal installations but I find that eventually I am missing a package at a later date. Full ends up saving me time in the end.

1 members found this post helpful.

I don't ever use tag files. I usually just install everything except for e, f, k, kde, kdei, t, xap, xfce, and y, and then add on whatever I need from there. Usually it is not much, as I get the rest from SBo, Alien Bob, or my own SlackBuild scripts.

Man, you have managed to put into a few words what Slackware means to you and also to me.

I only do full installs

1 members found this post helpful.

I would use shorter version in my signature. Thanks. Or tattoo on my body. For my girlfriend.

I just install everything except KDE and KDEI. If I need someting from KDE, I'll install kdelibs, oxygen-icon-theme and kde-l10n-es and then install whatever I need. Marble is nice.

"Me too" .. my usual practice is to install everything except kde/ and kdei/.

I've dorked around with tagfiles trying to come up with a "generic do-everything server" that fits nicely on small VM instances, but without much success. Eventually I give up, bite the bullet, shell out $$ for a larger VM instance, and install everything except kde/ and kdei/.

I once found it to be advantageous to have a minimal bare install from the slow install media.

Once up and running I installed everything else (as usual).

Could have benefited from less than a, l, and n in that it would save me time.

Other than that, the container installation process could benefit from an tag file as well - the same bare minimum:

To be able to boot, rise the network, be able to ssh into it and wget and installpkg.

A similar tag file could be useful for building a build-root that can bootstrap a build process (the famous circular dependency)

It is very clear to me that the benefiting group is small in the overall community, but had we have it - who knows maybe other users could find benefit in using it too?

1 members found this post helpful.

i normaly install everything besides kde and kdei atleast for server use.. on a desktop i do a real everything install.
so i never needed TAG Files.

I hope ARM Slackers come soon

WOW!

That's first time I see someone here agreeing that the lack of modularity of Slackware may result in supplementary costs for particular large VMs needed to install useless additional software.

1 members found this post helpful.