Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Add dependency on gzip to lxc for runtime
Date: Thu, 17 Sep 2015 19:16:00 +0200	[thread overview]
Message-ID: <20150917191600.06f9557d@free-electrons.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1509171816500.13941@orcam81.orcam.lan>

Hello,

On Thu, 17 Sep 2015 18:20:34 +0300 (IDT), Jonathan Ben Avraham wrote:

> > Date: Thu, 17 Sep 2015 18:03:53 +0300
> > From: Baruch Siach <baruch@tkos.co.il>
> > To: Jonathan Ben-Avraham <yba@tkos.co.il>
> > Cc: buildroot at buildroot.org
> > Subject: Re: [Buildroot] [PATCH 2/2] Add dependency on gzip to lxc for runtime
> > 
> > Hi Yonatan,
> >
> > On Thu, Sep 17, 2015 at 05:46:33PM +0300, Jonathan Ben-Avraham wrote:
> >> From: Jonathan Ben Avraham <yba@tkos.co.il>
> >>
> >> lxc executables such as lxc-checkconfig require scripts provided by
> >> gzip such as zgrep.
> >>
> >> Signed-off-by: Jonathan Ben Avraham <yba@tkos.co.il>
> >> ---
> >>  package/lxc/Config.in |    6 ++++--
> >>  1 file changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/package/lxc/Config.in b/package/lxc/Config.in
> >> index ffd9b4a..e774eee 100644
> >> --- a/package/lxc/Config.in
> >> +++ b/package/lxc/Config.in
> >> @@ -9,6 +9,7 @@ config BR2_PACKAGE_LXC
> >>  	depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII201305
> >>  	depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII201405
> >>  	depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0 # libcap
> >> +	depends on BR2_PACKAGE_GZIP
> >
> > We generally use 'select' for non obvious dependencies like this one. You'll
> > also need to propagate the wchar dependency of gzip here.
> 
> I didn't use 'select' because of its implicit, sneaky nature. Bash is too 
> heavy to just "select" it into a rootfs without the user explicitly 
> putting an 'X' in the checkbox.

Still, we want such dependencies to use a "select" like Baruch said.
They should even be noted this way:

	select BR2_PACKAGE_GZIP # runtime dep only

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-09-17 17:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 14:46 [Buildroot] [PATCH 1/2] Add dependency on bash to gzip for runtime Jonathan Ben-Avraham
2015-09-17 14:46 ` [Buildroot] [PATCH 2/2] Add dependency on gzip to lxc " Jonathan Ben-Avraham
2015-09-17 15:03   ` Baruch Siach
2015-09-17 15:20     ` Jonathan Ben Avraham
2015-09-17 17:16       ` Thomas Petazzoni [this message]
2015-09-17 15:01 ` [Buildroot] [PATCH 1/2] Add dependency on bash to gzip " Baruch Siach
2015-09-17 15:16   ` Jonathan Ben Avraham
2015-09-17 16:20     ` Baruch Siach
2015-09-17 16:33       ` Jonathan Ben Avraham
2015-09-17 17:23         ` Thomas Petazzoni
2015-09-17 19:04           ` Baruch Siach
2015-09-17 20:15             ` Thomas Petazzoni
2015-09-19 20:36               ` Jonathan Ben Avraham
2015-09-20  8:22                 ` Thomas Petazzoni
2015-09-20 10:39                   ` Arnout Vandecappelle
2015-09-20 11:16                     ` Thomas Petazzoni
2015-09-20 11:35                       ` Baruch Siach

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=20150917191600.06f9557d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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