From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] busybox: enable CONFIG_BZIP2/CONFIG_XZ/CONFIG_UNXZ by default
Date: Wed, 24 Sep 2014 18:46:00 +0800 [thread overview]
Message-ID: <5422A0E8.1010506@windriver.com> (raw)
In-Reply-To: <CAJTo0LZcTFqhyWKTcYiWDHUCP-zKsYucnjPx9J1yjA3Zi66rvg@mail.gmail.com>
On 09/23/2014 10:47 PM, Burton, Ross wrote:
> On 23 September 2014 15:19, Hongxu Jia <hongxu.jia@windriver.com> wrote:
>> It was required by info/man command to compress/decompress
>> doc pages with xz/bz2 compression.
> When changing busybox configuration, it's helpful to list the size change.
>
> So for anyone else curious, buildhistory reports the package size (not
> the binary size) as:
>
> -PKGSIZE = 573632
> +PKGSIZE = 585144
Since we care about the size, and affect of the fix is global.
How about conditionally add 'xz/bz2/gzip' to info/man's
RDEPENDS according DOC_COMPRESS value.
V2 incoming
//Hongxu
> Ross
next prev parent reply other threads:[~2014-09-24 10:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:19 [PATCH 0/3] man/info: fix not support xz/bz2 compression Hongxu Jia
2014-09-23 14:19 ` [PATCH 1/3] busybox: enable CONFIG_BZIP2/CONFIG_XZ/CONFIG_UNXZ by default Hongxu Jia
2014-09-23 14:47 ` Burton, Ross
2014-09-24 10:46 ` Hongxu Jia [this message]
2014-09-23 14:19 ` [PATCH 2/3] man: fix not support xz/bz2 compression Hongxu Jia
2014-09-23 14:19 ` [PATCH 3/3] texinfo: fix info not work Hongxu Jia
2014-09-23 14:52 ` Burton, Ross
2014-09-23 20:37 ` Richard Purdie
2014-09-23 20:40 ` Burton, Ross
2014-09-24 9:16 ` Hongxu Jia
2014-09-24 10:50 ` Burton, Ross
2014-09-24 8:58 ` Hongxu Jia
2014-09-23 15:16 ` [PATCH 0/3] man/info: fix not support xz/bz2 compression Mark Hatle
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=5422A0E8.1010506@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.