I don t think so myself. I learned so much from just installing in on so many different ocasions. I m also planning to get back to my old slackware on my farely low end MSI Wind U90X netbook sometime this week. I also plan to make a seedbox and help the community with the ISO seeding of both -current and -stable images.
So yeah, welcome back into my life Slackware, i missed you so much <3 "bloated" as you are !:d

cannot agree more

I don't think Slackware is bloated, but there are some packages I'm curious about. Why are they included and does anybody even use them?

virtuoso-ose
raptor
rasqal
redland
obex*


does anyone actually use any of these, and if so, what for? I've asked for Postgresql before, which I'd be willing to bet is much more popular than virtuoso, but we have virtuoso and not PG. Or am I wrong about its popularity?

-Andy

You can't narrow down a list of pre-installed packages that will satisfy every user's needs.

That being said, I do use the obex-* packages to transfer files between my Android phone and my PC through a Bluetooth connexion.

It's rather easy for me to set a Bluetooth connexion than messing around with the MTP protocol crap.

I think that the fact that Slackware comes with packages for both desktop and server usage might be self-explanatory. :hattip:

Not to mention that when you become more experienced with Slack, you can set your own tagfiles up. ;)

Some people also share their own config in that regard.

Don't get me wrong, I understand Slackware needs to have a range of packages for different users. That's cool, and I don't care that virtuoso and the others are included, nor that I turn around and always uninstall them.

What I'm wondering is why they got included. What is popularity? Just a whim? $$$? If I can understand that, maybe I can get Postgresql included. See?

-Andy

Codeguy, there's a description of each package in PACKAGES.TXT. You can look them up there:

http://slackware.osuosl.org/slackwar...1/PACKAGES.TXT

A scan through that tells me that obex is there for Bluetooth support.

Except obex* all others + soprano strigi akonadi phonon* libbluedevil qimageblitz are used ONLY by KDE. So the right question is why this stuff is not moved from /l to /kde.

And also why can't we have for example /l-gui with all the gtk-1,2,3 + atk + pango + cayro + qt + pygtk + pyqt stuff. And may be /l-av for the audio/video libraries. And may be /x-scim for those who need it and maybe /x-drivers for all the xf86-input-* and xf86-video-* packages and /n-bluetooth for bluez* and obex* and /n-wifi for all the wifi stuff and /n-wifi-firmware for the firmware stuff and /ap-database for mariadb and postgresql (it's a shame to not have it).

And /ap-workbone for our special quest :)

Slackware as a whole is not bloated. You don't even get libreoffice by default. But may be after some 20 years the tree needs several new branches.

Cheers.

hahaha nice! love it! Where did you get the sticker?

They can be found at the Slackware Store. I can vouch that the sticker looks great on a tower too. Certainly an upgrade of the Corsair plate that came with my case.

I'm just going to go out on a limb and say that I'd be okay with Slackware dropping PCMCIA support.

in other words, "I don't use it, why ship it?" :D

Prediction: the support for PCMCIA will be removed from Slackware 100.

Workaround: chmod -x /etc/rc.d/rc.pcmcia

Local fix: remove the package pcmciautils, remove the support for pcmcia in the kernel you use (and modules), remove the script /bin/pcmcia in the installer as well as all you'll find running at the root of the initrd "find -iname "*pcmcia*", remove all pcmcia stuff from usb.ids and pci.ids. I certainly forgot a lot of necessary cleaning, sorry about that ;)

I have quite a few machines that depend on PCMCIA for network or wireless, and a few odd other things.

Admittedly, most of those will not likely be reinstalled with a newer Slackware, but it could happen - and I am certainly glad it wasn't dropped from earlier versions!

PCMCIA support is tiny (AFAICT) and the drivers are all modules, so why pick on PCMCIA? ;)