public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <cyklonite@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "X11 forwarding" so to say ... but for audio
Date: Tue, 19 Jul 2016 10:13:59 -0400	[thread overview]
Message-ID: <db07c3cf-f356-53b3-87ac-7f443c9864d0@gmail.com> (raw)
In-Reply-To: <20160719131714.23564621@hactar.digimed.co.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/19/2016 08:17 AM, Neil Bothwick wrote:
> On Tue, 19 Jul 2016 07:21:33 -0400, Fernando Rodriguez wrote:
> 
>>>>   The following REQUIRED_USE flag constraints are unsatisfied:
>>>>     client? ( x264? ( dec_av2 ) x265? ( dec_av2 ) )  
>>>
>>> It means that if you have client you need x264 and x265 and those both
>>> require dec_av2, which is the one you don't have set.
>>>
>>>   
>>
>> I thought it meant that if you have client AND (x264 OR x265) then you
>> need dec_av2. client doesn't require x264 or x265 by itself.
> 
> Doesn't that use || ? Anyway, he has client and x264, so dec_av2 is
> needed.
> 

No, || means "any of", see [1]. And I believe in that case portage will translate
it to "any-of" or something like that. These are just nested conditionals. It can
be confusing even for someone with programming background. I suppose portage
could translate that into a more human friendly form but with many nesting levels
it will get ugly any way you put it.

And yes, dec_av2 is what he needs (unless he doesn't need x264 and x265 support).
I was just clearing the point about the meaning of the message.

[1] https://devmanual.gentoo.org/general-concepts/dependencies/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXjjWmAAoJEPbOFX/5UlwcEvsP/RMEbpNJlJIbNHDIk5AANnlG
/gox+r/K1/NWJ003WHtdHNNXZURa7jJrDoAsPbZ4fplbezdNNteLThYXJl1BA75G
OZfc/M7zB3TeHSaTDPwTwCfUUZPsicc5CttPwgh127VcXLct+IV8TbDXiD31gK0U
56Shl54Fh5cymuBt3hrtUj4hBtczUITWHL2US6RRcKHHVkHmGGOKNiumXYTbt4Op
w42htuFyXIvvIOCUZxM700nrw6yU/Cv7OCEps1pHor9V2lYYPgX+88U4tBWogOiN
voFaUUkkqMt2y/3zo0KmKABb4JjKTa3ros/0x1UFck9wuMCyvf23i1f1hGhU3Ea/
mq5XcTDO6oukPxpmQGveMT3NiS8vGyXkORPnOW8rT9dqJoivkYOK/5M9nZBlGIkq
dfzbgbA664iDADxf1W4fdzjUXv5WYPgafqnhkmAbXkkCOZmvFFrZ6dupOe1rfJvV
hg3IVAiO+Ape3vPbpd0gzHqzV+1TQGc/ljNF1XXW83Jp4LcslKZ1QZ3mFJ07LlQ+
qQN+Iwu9L6JkohI+5VjwsT++YnooSIW7y3j4SKjR+peCV7GizqSJi7z+oT2spF6E
2lKhHDzb2Cpme0SuZFntytfjxYmg0G7UuAqNBMgP+Ep9iFpFXh22LdlTb32fEvMX
toW7DP5Eln2Qq8LWW9/B
=mUPb
-----END PGP SIGNATURE-----


  reply	other threads:[~2016-07-19 14:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  5:16 [gentoo-user] "X11 forwarding" so to say ... but for audio Meino.Cramer
2016-07-18  5:23 ` Fernando Rodriguez
2016-07-18  5:52   ` Meino.Cramer
2016-07-18 14:19     ` Erik Marsk
2016-07-19  2:33 ` Stroller
2016-07-19  5:08   ` Meino.Cramer
2016-07-19  7:49     ` Neil Bothwick
2016-07-19 11:21       ` Fernando Rodriguez
2016-07-19 12:17         ` Neil Bothwick
2016-07-19 14:13           ` Fernando Rodriguez [this message]
2016-07-19 14:37             ` Meino.Cramer
2016-07-19 15:34               ` Fernando Rodriguez
2016-07-19 16:08                 ` Meino.Cramer
2016-07-19 16:30                   ` Marc Joliet
2016-07-19 16:53                     ` Fernando Rodriguez
2016-07-19 16:33                   ` Fernando Rodriguez
2016-07-19 17:00 ` [gentoo-user] " James

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=db07c3cf-f356-53b3-87ac-7f443c9864d0@gmail.com \
    --to=cyklonite@gmail.com \
    --cc=gentoo-user@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