2 ms·
> ... unsuccessfully because "customers don't need it ..." And yet, as I noticed (yet again) earlier today while working on kickstarts, it is impossible to get
by jlgaddis 9y ago
> ... unsuccessfully because "customers don't need it ..."
And yet, as I noticed (yet again) earlier today while working on kickstarts, it is impossible to get rid of some packages that I will never want installed because they are listed as required dependencies when they really should be, at most, "recommends".
For example, I'm currently putting together a kickstart file for a minimal "desktop" installation on ThinkPads -- well, as minimal as RHEL will let me, that is (which isn't saying much). There are numerous packages that I absolutely do not want on these systems but that I am stuck with, such as: bluez, cups-{libs,pk-helper}, gnome-bluetooth{,-libs}, gnome-online-accounts, libsmbclient, oddjob-mkhomedir, samba-{client-libs,common}, tigervnc-{license,server-minimal}, and probably some others that I'm forgetting at the moment.
A few of these -- the Bluetooth-related ones -- are particularly relevant [0], yet I can't uninstall these packages (or, better yet, avoid installing them in the first place) without rpm/yum insisting on also taking out dozens of other, critical packages (no, "--nodeps" is not an acceptable solution). Yes, I can "hack" my way around it (disabling services/unit files, etc.) but it would be great if one didn't have to do that in the first place.
Sorry, this wasn't directed at you personally, but rather Red Hat in general.
> ...fought unsuccessfully to include some package in RHEL6 ...
On a side note, I'm now curious which package you were referring to.
</rant>
- bonzini 9y agoThe ACPI assembler if I remember correctly. BTW, an easy way to block Bluetooth is blacklisting the kernel module. RPM only got soft dependencies recently, so maybe you can check whether Fedora uses them for Bluetooth userspace packages and similar.
- jlgaddis 9y agoYeah, the "bluetooth" module is one of several that I disable ("install bluetooth /bin/true" in /etc/modprobe.d/disabled.conf) but -- from a paranoid security perspective -- I'd much prefer to not have the software installed in the place. I also have BT disabled in the BIOS. Many, many years ago I'd compile my own kernels and leave out all the stuff I didn't want but that's not worth my time nowadays.