From: Alec Warner <antarus@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Try to specify how to get that a USE flag is present in current ebuild
Date: Sun, 23 Sep 2012 05:52:05 +0000 [thread overview]
Message-ID: <CAAr7Pr9mr1nP4DHzALj03sxBGZjpxff_ikJcJ-K890+=iwUvcQ@mail.gmail.com> (raw)
In-Reply-To: <1348341756.2085.24.camel@belkin4>
On Sat, Sep 22, 2012 at 7:22 PM, Pacho Ramos <pacho@gentoo.org> wrote:
> El sáb, 22-09-2012 a las 13:54 -0400, Mike Frysinger escribió:
>> On Friday 21 September 2012 15:08:20 Pacho Ramos wrote:
>> > In that one, we try to use the following:
>> > has vala ${IUSE//+/} && ! use vala && return 0
>>
>> inherit eutils
>> use_if_iuse vala
>> -mike
>
> I am aware of that one also, but Ciaran also wants to forbid it for the
> same reason :S
Well I assume Ciaran wants to forbid it because he is attempting to
write a PMS compliant PM; but in order to use these ebuilds properly
he has to emulate the unspecified behavior that the ebuilds rely on
upon. His claim is that the council is supposed to forbid this
behavior (presumably to make his job less horrible) but I don't see
them beating down your door to change it (and the behavior is not
new.)
-A
next prev parent reply other threads:[~2012-09-23 6:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 19:08 [gentoo-portage-dev] Try to specify how to get that a USE flag is present in current ebuild Pacho Ramos
2012-09-21 19:45 ` Zac Medico
2012-09-21 20:26 ` Pacho Ramos
2012-09-21 20:32 ` Zac Medico
2012-09-21 20:38 ` Brian Harring
2012-09-21 20:44 ` Zac Medico
2012-09-22 17:54 ` Mike Frysinger
2012-09-22 19:22 ` Pacho Ramos
2012-09-23 5:52 ` Alec Warner [this message]
2012-09-23 7:36 ` Pacho Ramos
2012-10-05 17:41 ` Pacho Ramos
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='CAAr7Pr9mr1nP4DHzALj03sxBGZjpxff_ikJcJ-K890+=iwUvcQ@mail.gmail.com' \
--to=antarus@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