public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Bartłomiej Burdukiewicz" <bartlomiej.burdukiewicz@gmail.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Anuj Mittal <anuj.mittal@intel.com>
Subject: Re: [OE-core] [meta-oe][PATCH] libva: Removed virtual/mesa dependency
Date: Wed, 29 Apr 2020 13:50:19 +0200	[thread overview]
Message-ID: <2195913.ElGaqSPkdT@navi> (raw)
In-Reply-To: <376f53f97f8eed5797ddb21d52fe8e0b5b9fc87f.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

On Wed, 28 Apr 2020 10:47:42 CEST Richard Purdie wrote:
> On Tue, 2020-04-28 at 01:09 +0200, Bartłomiej Burdukiewicz wrote:
> > Other media player don't have strong requirements for GLX.
> > 
> > I'm now totally unsure. Probably adding PACKAGECONFIG with glx flag
> > (disabled
> > by default) will be better approach with conditional virtual/mesa
> > dependency.
> > This will fix recursive dependency problem for common cases. There is
> > also ton
> > of articles that GLX is deprecated, so softly going away should be a
> > proper
> > way.
> > 
> > Or just those bbappends should stay where they are. Another thing is
> > that
> > meta-intel layer introduced libva-intel package which also need
> > separate
> > bbappend to remove virtual/mesa, this made me to post that patch in
> > first
> > place.
> 
> Turning it into a PACKAGECONFIG is definitely a good idea and I'm happy
> to have a patch to do that. What the defaults should be I'm less sure
> about, initially leaving as it is today, maybe discuss changing the
> default in a follow up second patch?
> 
> Cheers,
> 
> Richard

Ok sounds reasonable, I'll prepare new patch and do some testing around it.

Thanks,
Bartłomiej 

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

  reply	other threads:[~2020-04-29 11:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 15:01 [meta-oe][PATCH] libva: Removed virtual/mesa dependency bartlomiej.burdukiewicz
2020-04-25  4:46 ` [OE-core] " Khem Raj
2020-04-25 19:38   ` Bartłomiej Burdukiewicz
2020-04-25 23:03     ` [OE-core] " Fred Baksik
2020-04-26  4:23     ` Anuj Mittal
2020-04-27 23:09       ` Bartłomiej Burdukiewicz
2020-04-28  8:47         ` Richard Purdie
2020-04-29 11:50           ` Bartłomiej Burdukiewicz [this message]
2020-05-06 12:41 ` Zoltan Boszormenyi
2020-05-07 11:25   ` Bartłomiej Burdukiewicz
2020-05-07 11:48   ` Richard Purdie
2020-05-07 12:47     ` Zoltan Boszormenyi

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=2195913.ElGaqSPkdT@navi \
    --to=bartlomiej.burdukiewicz@gmail.com \
    --cc=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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