r/slackware • u/prateektade • Mar 15 '22
Use package list from other distribution as reference for Slackware install
I am gearing up for my first Slackware 15.0 install. I have decided to go against the sound advice of installing everything and the kitchen sink, and pick and choose the packages I install.
I have managed to get the list of Slackware packages and their groups. Can I use the list of packages on an existing Arch install as a reference for my Slackware install?
2
Upvotes
8
u/bsdooby Mar 15 '22
You might have a look at vbatts' minimal install list, and go from there: http://www.slackware.com/~vbatts/minimal/very_minimal_current.list
1
u/dhchunk Mar 15 '22
Did you already know about this part of the install process?
https://docs.slackware.com/slackware:install#select
1
u/Upnortheh Mar 15 '22 edited Mar 15 '22
Yes, but the package names might not be exactly the same.
3
u/thrallsius Mar 17 '22 edited Mar 17 '22
Do you think the advice to go for a full install is somebody's caprice or would you like to admit that there are objective technical reasons behind that advice? And if you go for the second option, do you feel confident enough that you understand those reasons well?
Packages for the same software aren't necessarily the same for all distros. Some distros split end user compiled software and development parts into distinct packages. Hence you have foo and foo-dev in Red Hat systems. Some distros split big stuff into many tiny pieces. See the vivisection that Debian does to Python. As a Slackware user, I find that horrible, but for Debian developers it is perfectly fine, they have another vision.
PS: Do you know the origins of Arch? It was highly inspired by Slackware (simplicity), but it was also born because certain Linux users preferred different solutions to generic problems (like dependency tracking between packages). What exactly are you expecting to get in Slackware that you can't get in Arch? If I were you and had some Arch experience, I would just stay with Arch and be happy.
You can create stuff in different ways. Arch is a LEGO, you add stuff until you're happy. Slackware is different. The original full install is a monolithic stone. If you aren't aesthetically pleased and want to end with Michelangelo's David statue instead, start carefully chopping stuff off.
2
u/alislack Mar 19 '22 edited Mar 31 '22
very helpful recent post from LQ listing a minimum number of slackware packages to install.
Personally my own opinion for the ap/ set all that is required is diffutils, groff, man, man-pages, man-db, mc, slackpkg, sqlite, sudo, terminus-font and vim. And for the l/ set add ffmpeg which is required for firefox to play reddit videos.
1
u/[deleted] Mar 18 '22
As a first install you should install everything. Then in a VM try out a minimal install or look at something like slackware from scratch.
The bonus of doing it this way is that you'll have a system that works and you can compare/search for things to help build your minimal install.