From: Phil Blundell <pb@pbcl.net>
To: Christopher Larson <kergoth@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/6] libglu: add opengl to REQUIRED_DISTRO_FEATURES
Date: Wed, 04 Jan 2017 23:34:04 +0000 [thread overview]
Message-ID: <1483572844.4360.177.camel@pbcl.net> (raw)
In-Reply-To: <0f858d235ef2116b29251f6e471abdb62490532d.1483570577.git.chris_larson@mentor.com>
On Wed, 2017-01-04 at 15:57 -0700, Christopher Larson wrote:
>
> # Requires libGL.so which is provided by mesa when x11 in
> DISTRO_FEATURES
> -REQUIRED_DISTRO_FEATURES = "x11"
> +REQUIRED_DISTRO_FEATURES = "x11 opengl"
I sort of have the sense that something has gone a bit wrong with the
way {REQUIRED_}DISTRO_FEATURES is now being used.
The original concept with DISTRO_FEATURES was that it would just be a
global way of controlling the PACKAGECONFIG options for each recipe.
That is, if you have x11 in DISTRO_FEATURES then PACKAGECONFIG[x11]
would be turned on automatically for every recipe that supports it, and
so on. It was never really intended to be, and I still feel it
probably ought not to be, a filtering mechanism.
Or, to put it another way, just because you don't have x11 in
DISTRO_FEATURES doesn't necessarily mean that your distro refuses to
support x11 at all. It ought simply to mean that you don't
want packages compiled with X11 support where this is avoidable.
But in the particular case above, if the comment is correct then the
presence of x11 in REQUIRED_DISTRO_FEATURES seems bogus by any
interpretation. If it's really true that libGLU simply "Requires
libGL.so" then either:
a) it ought to have nothing at all in REQUIRED_DISTRO_FEATURES and
simply express a dependency on virtual/libgl (which would be my
preference); or
b) it ought to mention only opengl in REQUIRED_DISTRO_FEATURES
p.
next prev parent reply other threads:[~2017-01-04 23:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 22:57 [PATCH 0/6] Add opengl to REQUIRED_DISTRO_FEATURES for some recipes Christopher Larson
2017-01-04 22:57 ` [PATCH 1/6] waffle: add opengl to REQUIRED_DISTRO_FEATURES Christopher Larson
2017-01-04 22:57 ` [PATCH 2/6] piglit: " Christopher Larson
2017-01-04 22:57 ` [PATCH 3/6] libglu: " Christopher Larson
2017-01-04 23:34 ` Phil Blundell [this message]
2017-01-04 22:57 ` [PATCH 4/6] eglinfo-x11: " Christopher Larson
2017-01-04 22:57 ` [PATCH 5/6] packagegroup-self-hosted: " Christopher Larson
2017-01-04 22:57 ` [PATCH 6/6] packagegroup-core-lsb: " Christopher Larson
2017-01-04 23:49 ` [PATCH 0/6] Add opengl to REQUIRED_DISTRO_FEATURES for some recipes Burton, Ross
2017-01-05 0:52 ` Khem Raj
2017-01-05 1:13 ` Christopher Larson
2017-01-05 1:27 ` Khem Raj
2017-01-05 7:32 ` Patrick Ohly
2017-01-05 8:51 ` Richard Purdie
2017-01-05 10:35 ` Patrick Ohly
2017-01-05 8:54 ` Richard Purdie
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=1483572844.4360.177.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=kergoth@gmail.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