From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch yem/providers
Date: Sat, 21 Dec 2013 18:35:15 +0100 [thread overview]
Message-ID: <20131221173515.GC3481@free.fr> (raw)
In-Reply-To: <20131220104904.7cb29c07@skate>
Thomas, All,
On 2013-12-20 10:49 +0100, Thomas Petazzoni spake thusly:
> On Fri, 20 Dec 2013 10:43:01 +0100, Yann E. MORIN wrote:
> > > I must say I really like this proposal! It both makes virtual packages
> > > better, and solves the BR2_EXTERNAL problem without making invasive
> > > changes in the package infrastructure.
> >
> > Note that I still intend to work on the post-pone patch, as this would
> > allow more integration of BR2_EXTERNAL.
>
> Like what?
I just have to clear a case where a new external package enables a
feature for a built-in package. So, br2-external could provide extra
./configure options for a built-in package.
But that has deep implications, especially if Buildroot is then
distributed as part of a compliance effort: only providing Buildroot and
not br2-external would not be compliant.
So, in fact, I don't think we should make that easy.
> > > A few minor questions:
> > >
> > > *) Shouldn't we use 'qstrip' when doing:
> > >
> > > POWERVR_DEPENDENCIES = $(BR2_PACKAGE_PROVIDES_POWERVR)
OK, I've fixed that now.
> > > *) The jpeg virtual package should also be converted in the same way.
> Don't know about cryptodev,
cryptodev is like jpeg: it provides a choice.
> but jpeg is really a virtual package,
I've now converted both of them, too.
> but
> it's true that it is handled in a different way than the OpenGL
> packages, in that jpeg/Config.in provides a choice between the
> different providers. Not sure what we want to do here. Maybe nothing, I
> don't know.
I think we should just convert them over to how other virtual packages
are implemented: there is nothing to prevent, eg. rpi-userland and
ti-gfx (both providers of EGL) to be selected at the same time.
OK, those are a bit special, since they are tied to the hardware, when
neither jpeg nor cryptodev are. But still, I think we should have a
single way of doing virtual packages.
Peter, what's your opinion?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-12-21 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 23:43 [Buildroot] [pull request] Pull request for branch yem/providers Yann E. MORIN
2013-12-19 23:43 ` [Buildroot] [PATCH 1/5] package/opengl/libegl: switch to package-defined providers Yann E. MORIN
2013-12-19 23:43 ` [Buildroot] [PATCH 2/5] package/opengl/libgles: " Yann E. MORIN
2013-12-19 23:43 ` [Buildroot] [PATCH 3/5] package/opengl/libopenvg: " Yann E. MORIN
2013-12-19 23:43 ` [Buildroot] [PATCH 4/5] package/opengl/libopenmax: " Yann E. MORIN
2013-12-19 23:43 ` [Buildroot] [PATCH 5/5] package/powervr: " Yann E. MORIN
2013-12-20 9:31 ` [Buildroot] [pull request] Pull request for branch yem/providers Thomas Petazzoni
2013-12-20 9:43 ` Yann E. MORIN
2013-12-20 9:49 ` Thomas Petazzoni
2013-12-21 17:35 ` Yann E. MORIN [this message]
2013-12-20 18:03 ` Yann E. MORIN
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=20131221173515.GC3481@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.