From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id D7C8960557 for ; Tue, 28 Oct 2014 22:22:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id s9SMLkbT014765; Tue, 28 Oct 2014 22:21:46 GMT Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YBQ3GxzssvTz; Tue, 28 Oct 2014 22:21:46 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id s9SMLhHv014762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Oct 2014 22:21:44 GMT Message-ID: <1414534938.7967.176.camel@ted> From: Richard Purdie To: Koen Kooi Date: Tue, 28 Oct 2014 22:22:18 +0000 In-Reply-To: References: <1414336254-22707-1-git-send-email-koen@dominion.thruhere.net> <18631FB3-E9CA-4DD0-BF5A-DB114D3B7422@dominion.thruhere.net> <473E6E55-239E-4EC8-813C-8494BEF78CED@dominion.thruhere.net> X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Cc: OE-core Subject: Re: [PATCH] base bbclass: add support for tar.lz X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 22:22:27 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Tue, 2014-10-28 at 10:36 +0100, Koen Kooi wrote: > > Op 27 okt. 2014, om 14:15 heeft Burton, Ross het volgende geschreven: > > > > > > On 27 October 2014 13:06, Koen Kooi 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