All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Qi.Chen@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] busybox: enable SEAMLESS_XZ by default
Date: Mon, 23 Dec 2013 11:33:55 -0800	[thread overview]
Message-ID: <52B89023.80209@linux.intel.com> (raw)
In-Reply-To: <2e053dfde8c5b774d5f20be0f1afd3b41200fb9e.1387787578.git.Qi.Chen@windriver.com>

On 12/23/2013 12:36 AM, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> We have enabled SEAMLESS_GZ and SEAMLESS_BZ2 in defconfig, it's
> reasonable for us to enable SEAMLESS_XZ as well. Otherwise, we
> couldn't extract tar.xz file while we could extract tar.gz file.
> Such situation would be somewhat confusing.
>
It's also important to note how much bigger the busybox image grows when 
adding a new config options, so what's the increase in # of bytes?

Thanks
	Sau!

> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>   meta/recipes-core/busybox/busybox/defconfig |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/busybox/busybox/defconfig b/meta/recipes-core/busybox/busybox/defconfig
> index f0e63c2..20cd147 100644
> --- a/meta/recipes-core/busybox/busybox/defconfig
> +++ b/meta/recipes-core/busybox/busybox/defconfig
> @@ -125,7 +125,7 @@ CONFIG_FEATURE_HWIB=y
>   #
>   # Archival Utilities
>   #
> -# CONFIG_FEATURE_SEAMLESS_XZ is not set
> +CONFIG_FEATURE_SEAMLESS_XZ=y
>   CONFIG_FEATURE_SEAMLESS_LZMA=y
>   CONFIG_FEATURE_SEAMLESS_BZ2=y
>   CONFIG_FEATURE_SEAMLESS_GZ=y
>


  reply	other threads:[~2013-12-23 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  8:36 [PATCH 0/2] Fixes for systemd's ptest Qi.Chen
2013-12-23  8:36 ` [PATCH 1/2] busybox: enable SEAMLESS_XZ by default Qi.Chen
2013-12-23 19:33   ` Saul Wold [this message]
2013-12-24  1:31     ` ChenQi
2013-12-23  8:36 ` [PATCH 2/2] systemd: fix ptest to make it able to run on target Qi.Chen

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=52B89023.80209@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Qi.Chen@windriver.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 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.