-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 06/04/13 11:27 AM, Ciaran McCreesh wrote:
I concurr. Plus it was decided a couple of months back that everyone should revbump or version bump when migrating to EAPI5 (if not all future EAPIs). The main issue, as I recall, with libpng system updates is that a regular system-update-and-revdep-rebuild tends to fail because packages need to be rebuilt during the middle of the system update. Although this IS manageable even for green end-users with a bit of hand-holding, ideally we want to avoid it as much as possible. AFAICT, it's just a matter of timing the migration of rdeps we bump to EAPI5 and slot-operator deps. If we wanted to, we could: 1. revbump-and-p.mask ~arch packages, and the unmask them all when libpng-1.6 is unmasked -- a common, grep'able comment in p.mask could be used to indicate this list of package atoms. 2. ~arch-keyword a revbump of stable packages, and mass-stabilize when libpng-1.6 goes stable. A tracker bug would probably be best for this. And of course, if the package has an update for other reasons in the meantime, then they can just hit the tree as per normal and be removed from the list(s) above. Thoughts? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFiEJIACgkQ2ugaI38ACPCmWAD/UPXBQd0JwmK++UeZKfbaUK6w tBkv+9sGVkQoJ3rGMfwA/ivRzMbrKJFoLH7TAsi0lGvIL4AQrgkVVv02oFKgRpaP =u0Qx -----END PGP SIGNATURE-----
