HOWTO indicates that removal of `triggerhappy` will remove `raspi-config`, which seems to not be the case.
Created by: grempe
The HOWTO indicates that thinning the system, by removing triggerhappy
will also remove raspi-config
program. This appears to no longer be the case:
Incorrect doc:
https://github.com/ntpsec/stratum-1-microserver-howto/blob/master/index.txt#L1083
Pointers to change in this dependency:
https://github.com/RPi-Distro/raspi-config/pull/27
Output when running # ./clockmaker --strip
:
me# ./clockmaker --strip
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
bluez-firmware
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
bluez* pi-bluetooth* triggerhappy*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 3,572 kB disk space will be freed.
(Reading database ... 39538 files and directories currently installed.)
Removing pi-bluetooth (0.1.10) ...
Removing bluez (5.43-2+rpt2+deb9u2) ...
Removing triggerhappy (0.5.0-1) ...
Warning: Stopping triggerhappy.service, but it can still be activated by:
triggerhappy.socket
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
(Reading database ... 39464 files and directories currently installed.)
Purging configuration files for pi-bluetooth (0.1.10) ...
Purging configuration files for triggerhappy (0.5.0-1) ...
Purging configuration files for bluez (5.43-2+rpt2+deb9u2) ...
Processing triggers for systemd (232-25+deb9u6) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
bluez-firmware
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 250 kB disk space will be freed.
(Reading database ... 39454 files and directories currently installed.)
Removing bluez-firmware (1.2-3+rpt6) ...
me# which raspi-config
/usr/bin/raspi-config
Perhaps the docs can be updated to reflect that removal of raspi-config
is no longer something to worry about.