-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/11/12 05:29 AM, Michał Górny wrote: > On Fri, 02 Nov 2012 10:22:44 +0100 Rémi Cardona <r...@gentoo.org> > wrote: > >> Le jeudi 01 novembre 2012 à 23:30 +0100, Michał Górny a écrit : >>> Do you have any ideas how to solve that kind of stalemate? >> >> How about a carefully crafted news item inviting users to enable >> the latest python version and to emerge -C argparse afterwards? > > Well, I think that solves only the issue when users have argparse > in their @world. If something still depends on it on their system, > it will be pulled in back with the REQUIRED_USE issue. > > The news item is probably basically the same as installing with > warnings, except that the latter would show only to affected > users, I guess. >
I wonder if maybe we should skip the REQUIRED_USE definition for such things.. I'm also wondering if maybe the argparse ebuild itself for a while should do a no-op install against the other pythons and just QA-Warn, asking the user to submit a bug with equery d argparse output -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlCT7/MACgkQ2ugaI38ACPCjNQD+NAARDQMqsJ/ZdqZ6p1C9Z26r Pn3TpKw//Fx/vH39Ri0BALzuaY4VggAHDTuhA8r+2oL7E7WbYdclJLNu4EV5Qa+7 =NEW/ -----END PGP SIGNATURE-----
