From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, vivo75@gmail.com
Subject: Re: [gentoo-dev] RFC how to handle disappearing USE in (portage) dependency calculation
Date: Fri, 07 Jun 2013 17:07:50 -0700 [thread overview]
Message-ID: <51B275D6.7020909@gentoo.org> (raw)
In-Reply-To: <51B1EB41.80404@gmail.com>
On 06/07/2013 07:16 AM, vivo75@gmail.com wrote:
> According to the now readed fine manual, the ebuilds seem to be right,
> llvm is EAPI=5, udis86-1.7-r1 is EAPI=4 and the previous one is EAPI=3,
> dependency should be considered enabled if absent.
> So the bug would be in portage, but the overzealous dep resolution seem
> to arise only with "--with-bdeps=y" so I'm not opening it a bug.
It sounds as though you've got pic in use.mask, because portage has
different handling for masked flags prior to EAPI 5, as described here:
https://bugs.gentoo.org/show_bug.cgi?id=442830#c3
--
Thanks,
Zac
prev parent reply other threads:[~2013-06-08 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 11:26 [gentoo-dev] RFC how to handle disappearing USE in (portage) dependency calculation vivo75
2013-06-07 12:11 ` Ciaran McCreesh
2013-06-07 12:37 ` Sergey Popov
2013-06-07 14:16 ` vivo75
2013-06-08 0:07 ` Zac Medico [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=51B275D6.7020909@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vivo75@gmail.com \
/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