From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] OpenGL packaging/staging policy
Date: Mon, 22 Oct 2012 21:25:51 +0100 [thread overview]
Message-ID: <5085ABCF.6010403@r-finger.com> (raw)
In-Reply-To: <CAJTo0LZ=Z803V-joHd17qeMqm3XaNGEnJavSeb=LBzqcLW9AbQ@mail.gmail.com>
On 22/10/12 20:27, Burton, Ross wrote:
> On 22 October 2012 18:19, Tomas Frydrych <tf+lists.yocto@r-finger.com> wrote:
>> Our
>> current difficulties stem directly from trying to pretend this is not
>> the case, or that mesa is somehow more than just *a* GL provider. IMHO
>> the correct thing to do here is:
>
> Mesa is the only free GL provider, which does make it useful in an
> open source build system.
Useful, yes, but not different. Having multiple providers is a normal
scenario that OE handles perfectly well; having a privileged provider
and bunch second class providers is a new scenario that serves no useful
purpose here -- you are creating the problem you are trying to solve.
> This would be the "complication packaging tricks" that I alluded to in
> the original mail.
There is nothing complicated about this; the fact that you cannot build
mesa GL without *staging* mesa EGL at the same time is broken which ever
way you look at it. Having only mesa to stage things is not a fix, it's
a work around, and one that punishes everyone else for the mesa mess. :-)
Tomas
next prev parent reply other threads:[~2012-10-22 20:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 16:35 [RFC] OpenGL packaging/staging policy Burton, Ross
2012-10-22 17:19 ` Tomas Frydrych
2012-10-22 19:27 ` Burton, Ross
2012-10-22 20:25 ` Tomas Frydrych [this message]
2012-10-23 2:06 ` Daniel Stone
2012-10-23 8:37 ` Tomas Frydrych
2012-10-23 9:18 ` Daniel Stone
2012-10-23 9:49 ` Tomas Frydrych
2012-10-29 17:26 ` Burton, Ross
2012-10-29 18:27 ` Tomas Frydrych
2012-11-20 16:52 ` Burton, Ross
2012-10-22 17:32 ` [oe] " Phil Blundell
2012-10-22 17:38 ` Otavio Salvador
2012-10-22 19:26 ` Burton, Ross
2012-10-22 17:33 ` Otavio Salvador
2012-10-22 19:25 ` Phil Blundell
2012-10-22 17:37 ` Mark Hatle
2012-10-22 19:29 ` Burton, Ross
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=5085ABCF.6010403@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=openembedded-core@lists.openembedded.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