From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] More >= atoms for autounmask USE changes (536392)
Date: Sun, 18 Jan 2015 09:05:07 -0800 [thread overview]
Message-ID: <20150118090507.3f518de9.dolsen@gentoo.org> (raw)
In-Reply-To: <1421565200-23147-1-git-send-email-zmedico@gentoo.org>
On Sat, 17 Jan 2015 23:13:20 -0800
Zac Medico <zmedico@gentoo.org> wrote:
> When checking for packages that will be matched by an autounmask USE
> change, account for package visibility (masking), so that we can
> generate more >= atoms (as opposed to = atoms that only match very
> specific versions). Don't do this for keyword or mask changes, since
> that may cause undesired versions to be unmasked!
>
> X-Gentoo-Bug: 536392
> X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=536392
> ---
> pym/_emerge/depgraph.py | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
looks good, merge please
--
Brian Dolbec <dolsen>
prev parent reply other threads:[~2015-01-18 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 7:13 [gentoo-portage-dev] [PATCH] More >= atoms for autounmask USE changes (536392) Zac Medico
2015-01-18 17:05 ` Brian Dolbec [this message]
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=20150118090507.3f518de9.dolsen@gentoo.org \
--to=dolsen@gentoo.org \
--cc=gentoo-portage-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