From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base bbclass: add support for tar.lz
Date: Tue, 28 Oct 2014 22:22:18 +0000 [thread overview]
Message-ID: <1414534938.7967.176.camel@ted> (raw)
In-Reply-To: <A5FC7B4F-F911-4DFA-8F66-C006740DC0F4@dominion.thruhere.net>
On Tue, 2014-10-28 at 10:36 +0100, Koen Kooi wrote:
> > Op 27 okt. 2014, om 14:15 heeft Burton, Ross <ross.burton@intel.com> het volgende geschreven:
> >
> >
> > On 27 October 2014 13:06, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > Ah, two different problems :/
> >
> > The problem that lzip-native isn't in oe-core is only a problem when there's a .lz SRC_URI in oe-core, but the false-positives are a problem now.
>
> Apart from this dependency problem, bitbake has a problem as well. Does anyone know why bitbake does:
>
> compressiontool --stdout file.tar.compressed | tar x
>
> instead of:
>
> tar xf file.tar.compressed
The unpack code is rather old, its age being around a decade. A decade
ago, tar without inbuilt decompression support was not uncommon. The
code has remained unchanged...
zlib was added, I know that most tar has bzip2 now. I'm not 100% sure
which formats we could rely on being in tar though. It would also be
interesting to know which performs better on a multicore system.
Cheers,
Richard
next prev parent reply other threads:[~2014-10-28 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 15:10 [PATCH] base bbclass: add support for tar.lz Koen Kooi
2014-10-27 10:59 ` Burton, Ross
2014-10-27 11:39 ` Koen Kooi
2014-10-27 11:54 ` Burton, Ross
2014-10-27 13:06 ` Koen Kooi
2014-10-27 13:15 ` Burton, Ross
2014-10-28 9:36 ` Koen Kooi
2014-10-28 22:22 ` Richard Purdie [this message]
2014-10-29 6:21 ` Koen Kooi
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=1414534938.7967.176.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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.