glibc should not be unemergeable or at least it should print a warning like when trying to unemerge portage or patch cheers...
This one's a portage bug. There was the hack in the glibc ebuild a while back, but portage is meant to warn on the attempted removal of system packages already. It doesn't do it for glibc because the profiles depend on the virtual rather than directly on the package.
Created attachment 52385 [details, diff] Expands virtuals and removes operators for syslist checking Pre-expands the syslist to include all known providers of a virtual for checking during the unmerge phase. Also kills of operators from the atoms so that only the raw cat/pkg is checked against.
If there's no complaints about the patch, it'll go into 2.0.51.19 some time down the line. There's another case that isn't accounted for which won't be handled until the next major version though. That is when a system package depends on another package that is not part of system - for example acl.
This is fixed enough for the time being. Anything in the system profile will be warned on.
