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] [PATCH 0/4] Do not select providers of virtual packages (branch yem/dont-select-providers)
Date: Thu, 17 Dec 2015 23:06:32 +0100	[thread overview]
Message-ID: <cover.1450389598.git.yann.morin.1998@free.fr> (raw)

Hello All!

This series fixes the selection of the Lua package, a sit is a provider
for the virtual package lua-interpreter.

As explained in the manual, it is not allowed to select the provider of
a virtual package. Quoting:

    If your package really requires a specific provider, then you?ll
    have to make your package depends on this provider; you can not
    select a provider.

Followed by an explanations on the reasons this should not be done:

    https://buildroot.org/downloads/manual/manual.html#_infrastructure_for_virtual_packages

This series just cleanups the situation with respect to the
lua-interpreter virtual package. It has not been checked if we
had other virtual packages for which providers were selected.
This can be done in a later series.

Regards,
Yann E. MORIN.


The following changes since commit aee53f8b6f29916ca5d322f793828c24874459d5:

  package/php: Always link with libpthread for static builds (2015-12-17 22:50:56 +0100)

are available in the git repository at:

  git://git.busybox.net/~ymorin/git/buildroot yem/dont-select-providers

for you to fetch changes up to cb0f7634e0c32e0e383baa52e48047dc7a82b7ea:

  package/libedje: do not select Lua, depend on it (2015-12-17 22:58:46 +0100)

----------------------------------------------------------------
Yann E. MORIN (4):
      package/dnsmasq: do not select Lua, depend on it
      package/haserl: do not select Lua, depend on it
      package/lighttpd: do not select Lua, depend on it
      package/libedje: do not select Lua, depend on it

 package/dnsmasq/Config.in           |  5 ++++-
 package/efl/libedje/Config.in       |  6 +++---
 package/efl/libelementary/Config.in |  6 ++++--
 package/efl/libethumb/Config.in     |  5 +++--
 package/enlightenment/Config.in     |  6 ++++--
 package/haserl/Config.in            | 10 ++++++++--
 package/lighttpd/Config.in          |  5 ++++-
 7 files changed, 30 insertions(+), 13 deletions(-)

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

             reply	other threads:[~2015-12-17 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 22:06 Yann E. MORIN [this message]
2015-12-17 22:06 ` [Buildroot] [PATCH 1/4] package/dnsmasq: do not select Lua, depend on it Yann E. MORIN
2015-12-17 22:08   ` Thomas Petazzoni
2015-12-17 22:06 ` [Buildroot] [PATCH 2/4] package/haserl: " Yann E. MORIN
2015-12-17 22:06 ` [Buildroot] [PATCH 3/4] package/lighttpd: " Yann E. MORIN
2015-12-17 22:06 ` [Buildroot] [PATCH 4/4] package/libedje: " 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=cover.1450389598.git.yann.morin.1998@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