"Michael P. Soulier" <msoul...@digitaltorque.ca> writes: > Sure enough, X no longer works. I'm following the instructions now, but... > Don't you think the default action here should be to do nothing instead of > breaking my system?
I think that the default action should be that such 'breakages' should be checked during the dependency building phase, a message displayed and the emerge stop[0]. Then you could either mask the offending package or issue a special flag[1] to emerge to acknowledge the 'problem' but install/upgrade the package anyway. [0] As with package blockers. [1] A new flag, something like '--unsafe'
