Package specific version dependencies

Package specific version dependencies

[Francesco Del Degan]

Hi all,

Playing with RDEPENDS variable i'm facing the needs to
specify a dependency based on specific version of a package
(greather than, in my specific case).

The underlying package managers supports declaring dependencies
including version relationships, for example:

Rpm:  Requires: package_xxx >= 1.0.27
Deb:  Depends: libc6 (>= 2.2.1)
Okpg: Depends: xfree (>= 6.0), glib2

Is this feature just missing in yocto or it's explicitly denied
for some reason?

In first case:
Could a patch (I will need to work on package*.bbclass i guess)
be useful for Yocto/OE?

What could be a good syntax for bitbake variable in order to specify
this?

Thanks,
  Francesco 'pr0gg3d' Del Degan

Re: Package specific version dependencies

[Paul Eggleton]

Hi Francesco,

On Tuesday 06 August 2013 09:55:06 Francesco Del Degan wrote:
> Playing with RDEPENDS variable i'm facing the needs to
> specify a dependency based on specific version of a package
> (greather than, in my specific case).
> 
> The underlying package managers supports declaring dependencies
> including version relationships, for example:
> 
> Rpm:  Requires: package_xxx >= 1.0.27
> Deb:  Depends: libc6 (>= 2.2.1)
> Okpg: Depends: xfree (>= 6.0), glib2
> 
> Is this feature just missing in yocto or it's explicitly denied
> for some reason?

This should work, in fact we use it (with =) in conjunction with EXTENDPKGV 
when we want to force packages from the same recipe to upgrade in lock-step.

Have you tried adding these specifications to an RDEPENDS value?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Package specific version dependencies

[Francesco Del Degan]

Paul Eggleton <paul.eggleton@linux.intel.com>
writes:

> Hi Francesco,
>
> On Tuesday 06 August 2013 09:55:06 Francesco Del Degan wrote:
>> Playing with RDEPENDS variable i'm facing the needs to
>> specify a dependency based on specific version of a package
>> (greather than, in my specific case).
>> 
>> The underlying package managers supports declaring dependencies
>> including version relationships, for example:
>> 
>> Rpm:  Requires: package_xxx >= 1.0.27
>> Deb:  Depends: libc6 (>= 2.2.1)
>> Okpg: Depends: xfree (>= 6.0), glib2
>> 
>> Is this feature just missing in yocto or it's explicitly denied
>> for some reason?
>
> This should work, in fact we use it (with =) in conjunction with EXTENDPKGV 
> when we want to force packages from the same recipe to upgrade in lock-step.
>
> Have you tried adding these specifications to an RDEPENDS value?

Great, works so good! I just looked at RDEPENDS variable documentation
and missed the examples and/or other recipes.

Thank you!
  Francesco

>
> Cheers,
> Paul

Re: Package specific version dependencies

[Mark Hatle]

On 8/6/13 4:07 AM, Paul Eggleton wrote:
> Hi Francesco,
>
> On Tuesday 06 August 2013 09:55:06 Francesco Del Degan wrote:
>> Playing with RDEPENDS variable i'm facing the needs to
>> specify a dependency based on specific version of a package
>> (greather than, in my specific case).
>>
>> The underlying package managers supports declaring dependencies
>> including version relationships, for example:
>>
>> Rpm:  Requires: package_xxx >= 1.0.27
>> Deb:  Depends: libc6 (>= 2.2.1)
>> Okpg: Depends: xfree (>= 6.0), glib2
>>
>> Is this feature just missing in yocto or it's explicitly denied
>> for some reason?
>
> This should work, in fact we use it (with =) in conjunction with EXTENDPKGV
> when we want to force packages from the same recipe to upgrade in lock-step.

The format for RDEPENDS is slightly different from all three.

dep (= ver)
dep (< ver)
dep (> ver)
dep (<= ver)
dep (>= ver)

(For those familiar with deb style, >> and << is not supported by the oe-core 
dependency set.  This is to avoid confusion as > and < are a lot more obvious.)

The items above are then mapped into their respective format depending on the 
package manager you have selected.

Note:  The version dependency items are not evaluated by bitbake, it only pays 
attention to the package name when determining build dependencies.  You would 
also need to specify (in your distribution or local .conf file) a 
PREFERRED_VERSION_dep = "ver" to ensure the right version is built.

--Mark

> Have you tried adding these specifications to an RDEPENDS value?
>
> Cheers,
> Paul
>

Re: Package specific version dependencies

[Francesco Del Degan]

Mark Hatle <mark.hatle@windriver.com> writes:

> On 8/6/13 4:07 AM, Paul Eggleton wrote:
>> Hi Francesco,
>>
>> On Tuesday 06 August 2013 09:55:06 Francesco Del Degan wrote:
>>> Playing with RDEPENDS variable i'm facing the needs to
>>> specify a dependency based on specific version of a package
>>> (greather than, in my specific case).
>>>
>>> The underlying package managers supports declaring dependencies
>>> including version relationships, for example:
>>>
>>> Rpm:  Requires: package_xxx >= 1.0.27
>>> Deb:  Depends: libc6 (>= 2.2.1)
>>> Okpg: Depends: xfree (>= 6.0), glib2
>>>
>>> Is this feature just missing in yocto or it's explicitly denied
>>> for some reason?
>>
>> This should work, in fact we use it (with =) in conjunction with EXTENDPKGV
>> when we want to force packages from the same recipe to upgrade in lock-step.
>
> The format for RDEPENDS is slightly different from all three.
>
> dep (= ver)
> dep (< ver)
> dep (> ver)
> dep (<= ver)
> dep (>= ver)
>
> (For those familiar with deb style, >> and << is not supported by the
> oe-core dependency set.  This is to avoid confusion as > and < are a
> lot more obvious.)
>
> The items above are then mapped into their respective format depending
> on the package manager you have selected.
>
> Note:  The version dependency items are not evaluated by bitbake, it
> only pays attention to the package name when determining build
> dependencies.  You would also need to specify (in your distribution or
> local .conf file) a PREFERRED_VERSION_dep = "ver" to ensure the right
> version is built.

Got it! Thank you for explanation.

Francesco