Wols Lists wrote: > On 25/07/21 14:49, Dale wrote: >> The problem here is that a user installed a package outside of >> emerge/portage's knowledge. > No that does *NOT* appear to be the problem. > > The problem is that the user installed - *using* *portage* - a package > that satisfied a critical system dependency. Except that they did not > intend for it to satisfy that dependency! > > If they HAD installed it outside of portage, they wouldn't have this > problem. > > Cheers, > Wol > >
That is another way of looking at it for sure. If Alan wants to install his mail program then maybe he should install the packages it depends on manually as well. My point was that emerge/portage has no way of knowing why he installed daemontools and to emerge/portage, that meant removing a package that the virtual no longer needed. To emerge/portage, having daemontools and openrc installed was no longer required. Since he installed daemontools, emerge/portage assumed that is what he wanted to use. Since emerge/portage is in the dark as to why, it's a expected behavior in my opinion. Either way, installing packages outside of emerge/portage puts the user in charge of the problems it creates. There's several ways to correct this so maybe one will be attractive enough to Alan to apply. I like Neil's myself but to each his own. Dale :-) :-)
