From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH, RFC]: automatically depend xz compressed URIs on xz-native [was: Re: bitbake: staging of binary over symlink breaks sysroot (lzma x xz)]
Date: Mon, 02 Aug 2010 13:23:43 -0700 [thread overview]
Message-ID: <4C57294F.3030804@mentor.com> (raw)
In-Reply-To: <20100802182044.GA6299@mx.loc>
Bernhard Reutner-Fischer wrote:
> On Mon, Aug 02, 2010 at 11:13:43AM -0700, Khem Raj wrote:
>> On (02/08/10 20:07), Bernhard Reutner-Fischer wrote:
>>> On Mon, Aug 02, 2010 at 10:49:10AM -0700, Khem Raj wrote:
>>>> On (02/08/10 19:13), Bernhard Reutner-Fischer wrote:
>>>>> On Wed, Jul 28, 2010 at 04:32:08PM +0200, Bernhard Reutner-Fischer wrote:
>>>>>> On Wed, Jul 28, 2010 at 04:06:13PM +0200, Bernhard Reutner-Fischer wrote:
>>>>>>> On Wed, Jul 28, 2010 at 03:39:33PM +0200, Marco Cavallini wrote:
>>>>>>>> Stanislav Brabec ha scritto, Il 28/07/2010 11:30:
>>>>> comments on the attached RFC patch?
>>>>> TIA,
>>>> -snip-
>>>>> @@ -420,12 +424,16 @@ python () {
>>>>>
>>>>> # unzip-native should already be staged before unpacking ZIP recipes
>>>>> need_unzip = bb.data.getVar('NEED_UNZIP_FOR_UNPACK', d, 1)
>>>>> - src_uri = bb.data.getVar('SRC_URI', d, 1)
>>>>>
>>>>> - if ".zip" in src_uri or need_unzip == "1":
>>>>> + if ".zip" in srcuri or need_unzip == "1":
>>>>> depends = bb.data.getVarFlag('do_unpack', 'depends', d) or ""
>>>>> depends = depends + " unzip-native:do_populate_sysroot"
>>>>> bb.data.setVarFlag('do_unpack', 'depends', depends, d)
>>>>> + for ext in ['xz']: #['gzip', 'bzip2', 'xz']:
>>>>> + if '.' + ext in srcuri:
>>>>> + depends = bb.data.getVarFlag('do_unpack', 'depends', d) or ""
>>>>> + depends += ' ' + ext + '-native:do_populate_sysroot'
>>>>> + bb.data.setVarFlag('do_unpack', 'depends', depends, d)
>>>> what does above hunk do.
>>> srcuri=proto://some.thing.tar.xz
>>> if ".xz" in srcuri then depend do_unpack on '
>>> xz-native:do_populate_sysroot'
>>>
>>> Re-reading the hunk it should better read:
>>> import re
>>> for (ext,tool) in [('xz','xz')]: # ('gz','gzip'),('bz','bzip2')
>> ^
>>
>> that will turn the rest into comment is that ok ?
>
> I didn't try the other two, so yes, it's ok.
Well, now that it's a tuple zip/unzip could go in there for sure, and we
leave gz/gzip and bz/bzip2 commented out for now. Later we could add
them, and put them into the default ASSUME_PROVIDED list in local.conf
or something...
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-08-02 20:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 9:30 bitbake: staging of binary over symlink breaks sysroot (lzma x xz) Stanislav Brabec
2010-07-28 9:52 ` Andrea Adami
2010-07-28 10:09 ` Marco Cavallini
2010-07-28 13:39 ` Marco Cavallini
2010-07-28 14:06 ` Bernhard Reutner-Fischer
2010-07-28 14:32 ` Bernhard Reutner-Fischer
2010-08-02 17:13 ` [PATCH, RFC]: automatically depend xz compressed URIs on xz-native [was: Re: bitbake: staging of binary over symlink breaks sysroot (lzma x xz)] Bernhard Reutner-Fischer
2010-08-02 17:49 ` Khem Raj
2010-08-02 18:07 ` Bernhard Reutner-Fischer
2010-08-02 18:13 ` Khem Raj
2010-08-02 18:20 ` Bernhard Reutner-Fischer
2010-08-02 20:23 ` Tom Rini [this message]
2010-08-04 10:37 ` [PATCH] base.bbclass: depend unpacking on native unpackers Bernhard Reutner-Fischer
2010-08-04 15:08 ` Khem Raj
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=4C57294F.3030804@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox