From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The problem with new dev-python/argparse and REQUIRED_USE
Date: Fri, 02 Nov 2012 12:08:19 -0400 [thread overview]
Message-ID: <5093EFF3.6090101@gentoo.org> (raw)
In-Reply-To: <20121102102955.5c8e4d7f@pomiocik.lan>
-----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 <remi@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-----
next prev parent reply other threads:[~2012-11-02 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 22:30 [gentoo-dev] The problem with new dev-python/argparse and REQUIRED_USE Michał Górny
2012-11-02 9:22 ` Rémi Cardona
2012-11-02 9:29 ` Michał Górny
2012-11-02 16:08 ` Ian Stakenvicius [this message]
2012-11-02 18:30 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5093EFF3.6090101@gentoo.org \
--to=axs@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox