Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch yem/providers
Date: Fri, 20 Dec 2013 19:03:30 +0100	[thread overview]
Message-ID: <20131220180330.GA3484@free.fr> (raw)
In-Reply-To: <20131220103143.53d1434e@skate>

Thomas, All,

On 2013-12-20 10:31 +0100, Thomas Petazzoni spake thusly:
> On Fri, 20 Dec 2013 00:43:23 +0100, Yann E. MORIN wrote:
> 
> > This series is a third attempt at trying to fix the BR2_EXTERNAL issue,
> > in that packages in BR2_EXTERNAL can't be providers of an implementation
> > for a virtual package, such as libegl.
[--SNIP--]
> A few minor questions:
[--SNIP--]
>  *) The jpeg virtual package should also be converted in the same way.

As you said, jpeg is also a virtual package. But since it is not written
the same way the others are, the change will be more involved than the
one done in this series.

So, I'd prefer this series (which is relatively simple) stays as-is, and
that once it is applied, we take care of jpeg (and cryptodev), by turning
them into "real virtual" packages (can't help but use that phrase of
yours, Gustavo! :-p).

>  *) In PATCH 1, in package/rpi-userland/Config.in, you're adding an if
>     BR2_PACKAGE_RPI_USERLAND ... endif block, but *before* the comment
>     related to the toolchain dependencies of rpi-userland. I never
>     remember if that is the situation causing indentation problem of the
>     comment in menuconfig or not. Would be good to check this.

Nope, since we're in a 'menu', not a 'menuconfig'.
The menu layout is still correct.

And even with a menuconfig, what is busted is if one option or a comment
is in the middle of other dependent options, such as:

    menuconfig FOO
        bool "foo"

    config BAR
        bool "bar"
        depends on FOO

    comment "FOO deps busted"

    config BUZ
        bool "buz"
        depends on FOO

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.  |
'------------------------------^-------^------------------^--------------------'

      parent reply	other threads:[~2013-12-20 18:03 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
2013-12-20 18:03   ` Yann E. MORIN [this message]

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=20131220180330.GA3484@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox