Why is bluetooth support one of the default packages in "Base" when doing an RHEL/CentOS server install? [closed]

This is an issue that has bugged me for a long time - why would the default server installation of RHEL?CentOS include desktop/laptop packages like bluetooth?

When using kickstart, I will usually start with the Base packages set, and then customize from there.

However, it seems counter-intuitive to me to put user-centric packages on a server - why is this done?

Unless there are Red Hat developers/product managers here, I don't think you'll get an answer justifying this. It's especially perplexing in the "Server" product.

Either way, it's trivial to remove the packages in %post, or Kickstart with %packages --nobase and start with a minimal installation and build up your package list from there.

Erase packages in %post that match yum search bluetooth:

yum erase bluez* gnome-bluetooth* pulseaudio-module-bluetooth

I find the server release to really be more of a "NO GUI" release.

You'll find other stuff in there too. (irda for example)

It seems reasonable that you might want to install a NO GUI install on an old laptop, so bluetooth might still be nice to have.

You can try installing just 'Core' and not 'Base'. %packages --nobase (but that may not be possible anymore)

You can also try building a custom kickstart that only includes the packages you really need.

I believe that the 'Server' install is a graphical desktop + server software. In other words it is largely a super set of desktop. It makes perfect sense for bluetooth support to be in a desktop since bluetooth accessories are getting more and more popular. In any case, I would expect that the performance penalty for having it is minimal while the convenience gain for things like home media servers is very big.

If you are in a situation where you want the fastest/most tuned Red Hat install, you should not be installing server anyways. You should be starting with a minimal install and adding in only the things that you need/use.