On Sun, Apr 10, 2022 at 07:17:42AM -0400, The Wanderer wrote: > On 2022-04-10 at 07:08, gene heskett wrote: > > > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote: > > >> I just don't install it. > > > > And how do you accomplish that? Its automatically installed AFAIK. > > And once installed, apt will not remove it without destroying the > > install. rm or chmod -x seems to be the only way, and nothing > > complains. > > What package(s), by exact name, are you referring to? That is, which > package(s) is it that produce this effect when you try to remove them? > > On my computer, I have several libavahi* packages, which could not be > removed without removing large swaths of packages - but I also have > avahi-daemon and avahi-utils, which can be removed with few if any side > effects (as far as triggering removal of other packages goes).
The lib* things are different. That's the price we pay for a binary distribution. I have quite a few libsystemd around. The alternative would be to compile everything. I'm not that uncompromising :) > And since the subject at hand in this branch of the thread appears to be > avahi-daemon, surely removing that single package should be enough to > prevent avahi from doing anything undesirable? Yes, that would be the one implementing zeroconf. As I see, gnome is listed as avahi-daemon dependency. So that could be what happens to Gene. "I'm going to remove Gnome now" does sound scary :) Cheers -- t
signature.asc
Description: PGP signature
