perl-core/Switch is now stabilized on "amd64 ppc x86", so this should be 
fixed.

> On 30/06/14 04:46 AM, Andreas K. Huettel wrote:
> > [snip!] * As Fabian pointed out, perl-core/Switch-2.160.0 should
> > still go stable. Fine with me (but I can't read your minds about
> > future stabilizations, and the virtual only had ~arch reverse
> > deps).
> 
> There shouldn't be any need to read minds, here -- if the previous
> stable perl had this capability, then the new stable perl should too
> (whether that be via internal or external module package).  If it
> doesn't, then the upgraded-new-stable-perl isn't a valid replacement
> for the stable version it previously replaced. Remember that there
> could be who knows what scripts on end-user systems that need this
> functionality, and if it's suddenly not available because the only
> thing that provides it is ~arch, then they are not left in a happy state..

I'm not fully buying this argument, since it would prevent us ever stabilizing 
a package where an upstream feature is removed. 

(Switch was first released with perl v5.7.3 and removed from v5.13.1. So there 
should have been lots of time to update dependency declarations or pull in the 
external package if needed for non-portage scripts.)

> It would be nice if something like a pkgmove be done on the virtual,
> though, upon its elimintation; anyone that installed the virtual to
> obtain perl Switch shouldn't have to unmerge and specifically emerge
> perl-core/Switch.  I'm not sure if pkgmove itself supports this, though..

I dont think this is what pkgmove does (this would move the "no installed 
files" vdb entry of the virtual to the perl-core name... we would need a 
functionality that only touches the world file alone...)

-- 
Andreas K. Huettel
Gentoo Linux developer
kde, council