Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: "Chang, Rebecca Swee Fun" <rebecca.swee.fun.chang@intel.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [master][PATCH] rpm: enable xz/lzma compression
Date: Thu, 17 Mar 2016 08:56:36 -0700	[thread overview]
Message-ID: <56EAD3B4.2080206@windriver.com> (raw)
In-Reply-To: <50B33AC5ED75F74F991980326F1C438D191CB5C4@PGSMSX103.gar.corp.intel.com>

On 3/14/16 1:18 AM, Chang, Rebecca Swee Fun wrote:
> We are having issues on decompressing tarball with xz format and rpm installation on target.
> We have this solution implemented to resolve it internally and would like to enable it in OE-core in order we wouldn't revisit this issue in future.
> Do I need to resend the patch with revised commit message?

When the packages are produced by the build environment then no issues should be
occurring.

The only time you should be having problems is if you are trying to install
packages (source or binary) produced from outside the build environment.  In the
source case, you can use the workaround of rpm2cpio <whatever> | cpio -id to
extract it.  Then when you build it fresh it will use the standard format.
(Yes, bz2/zlib is less efficient -- but is also more standard.)

If you require the xz/lzma compression, you should be doing this in your own
project's configuration.  I don't think it makes sense to add xz to all RPM
based filesystems.

(If you can profile what adding the xz option does to a filesystem, I may change
my mind.  The profiling needs to include the size change to RPM program itself,
the produced filesystem (as it now has additional dependencies), and the package
feeds size.

My guess, is:  RPM binary will increase in size marginally..  including XZ and
associated items could be potentially 'large'.. and the size of the package
feeds will be reduced, but I don't have a good feeling as to how much.

--Mark

> Regards,
> Rebecca
> 
> -----Original Message-----
> From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org] 
> Sent: Monday, March 14, 2016 4:14 PM
> To: Chang, Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [master][PATCH] rpm: enable xz/lzma compression
> 
> On Mon, 2016-03-14 at 15:15 +0800, Rebecca Chang wrote:
>> From: Anuj Mittal <anujx.mittal@intel.com>
>>
>> Enable lzma compression support in rpm.
> 
> Your commit message says what the patch does but not why? Presumably this change increases the size of the rpm install so what is the benefit?
> 
> Cheers,
> 
> Richard
> 



  reply	other threads:[~2016-03-17 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  7:15 [master][PATCH] rpm: enable xz/lzma compression Rebecca Chang
2016-03-14  8:13 ` Richard Purdie
2016-03-14  8:18   ` Chang, Rebecca Swee Fun
2016-03-17 15:56     ` Mark Hatle [this message]
2016-03-17 16:04       ` 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=56EAD3B4.2080206@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rebecca.swee.fun.chang@intel.com \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox