It didn't tell it clearly enough. The system was still bootable, albeit not graphically. Well, previous automated update has broken my bootloader config though. I still haven't got around to fixing it and have to enter the root path manually. It's rare because I keep the machine suspended most of the time.Matte88 wrote:I can't understand how a package manager could broke your system if the same tells you which packages will be removed (if there are deps) or blocks itself when recognize vital packages to be removed. Maybe I totally misunderstood the thread.
It said safe to remove, but the subtext in the log, AFTER hitting the button then said removing 1040 packages.
Are you supposed to sit there reading the logs after you hit a button that tells you it's safe to hit? I use a package manager to manage the packages for me. That's why I use a gentoo and not a slackware.
Explosively recursive reverse dependencies never happened like this with portage , certainly not by default.
Having said that the time saved by using pre-optimised binaries while allowing me to tweek with portage on occasion is will mean I still love and will stick with Sabayon. It didn't take long to recover from this in the end.