[oe] Python-native dependency in libxml2

[Frans Meulenbroeks]

2011/3/16 Khem Raj <raj.khem at gmail.com>:
> On 3/16/2011 12:28 AM, Frans Meulenbroeks wrote:
>>
>> 2011/3/16 Khem Raj<raj.khem at gmail.com>:
>>>
>>> On 3/15/2011 11:22 PM, Ahsan, Noor wrote:
>>>>
>>>> Hello,
>>>>
>>>> I was looking at the libxml2 package. While going through the recipes I
>>>> came to know that its native package depends on python-native package as
>>>> well. This dependency is defined in libxml2.inc file.
>>>>
>>>> DEPENDS_virtclass-native = "python-native"
>>>>
>>>> This package build fine after removing this dependency. I am not clear
>>>> why this dependency is being added in libxml2 package. Can somebody
>>>> clear that to me. While looking at the git log I came to know that this
>>>> change is coming from libxml2-native.inc file. But I am not clear why
>>>> this dependency was added as this package build fine without it.
>>>>
>>>> Please help me in understanding this dependency. Thanks.
>>>
>>> Try to build this recipe from scratch and see if it still works then we
>>> can
>>> remove the dep
>>
>> I'm not sure if that is the right way.
>> It might well be that typically python-native is already there in a
>> scratch build because some earlier package needed it (or even because
>> of the scheduling of build steps.
>>
>> Probably a better way is to build with packaged staging (with staging
>> dir outside TMPDIR) then rm TMPDIR and bake the package.
>> Alternately peek into the package to see if it needs python. If it is
>> needed then the DEPENDS should stay.
>
>
> Did you read carefully what I wrote ?

Yes. From scratch for me (and maybe also for others) means rm TMPDIR
(including pstaging).
In that case you might pick up stray packages.
You probably meant keeping pstaging, but at least for some of the
readers that is not obvious.

Frans