On Fri, Mar 23, 2007 at 09:31:39 -0400, Frank McCormick wrote:
[...]
> The strange thing is I **think** avahi-daemon was installed
> **before** KDE desktop was put on the machine. What I find strange is
> that Aptitude removed it when it wasn't installed as part of KDE.
That part is easy: Aptitude does not install dependencies as "part of"
anything. It just sets a flag in the package state database and thus
remembers "I installed this automatically, the user did not ask for this
package directly". All such "auto" packages will be removed as soon as
no other package on the system depends on them anymore. (This behavior
is of course configurable; you can, for example, tell aptitude that
"recommends" and "suggests" dependencies are enough to keep an "auto"
package on the system, or you can turn of the automatic removal
functionality completely.) If the removal of avahi-daemon was triggered
by the removal of KDE then kdenetwork was simply the last package on
your system which depended (indirectly) on avahi-daemon.
> Removing it was one thing - the network broke when the boot scripts
> called a script that's apparently part of the avahi-daemon package. Then
> DHCP stopped running, I guess because of the errors the boot script
> returned. I find the whole scenario utterly confusing.
It is normal for a package's initscripts to stay on the system after
removal. The scripts are treated as user-customizable configuration
files and as such they are only removed if a package is purged. However,
the scripts should of course be written such that they don't cause any
harm in this situation. What you saw might indeed be a bug of the
avahi-daemon package.
--
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
