On 20-09-09 10:40, Phil Blundell wrote:
On Sun, 2009-09-20 at 02:33 -0400, Denys Dmytriyenko wrote:
Fixes the wrong versioned runtime dependency for shlib subpackages with
own versions. Consider this:
PACKAGES = "libfoo libbar"
PV_libfoo = "1"
PV_libbar = "2"
PV = "3"
Is this even legitimate usage? I had always thought that PV applied to
the recipe, not to the output subpackages.
What's the typical use-case for this kind of thing?
It's usefull for the case where you have a meta-release (e.g.
codec-engine 2.24.01) containing itself (e.g. codec-engine), but also
matching parts like dsplink 1.63, lpm 1.14, etc. When building the
meta-release you'll get all the parts you need with matching versions,
but ideally you want the subpackages to keep their PV.
Another usecase would be a big external-toolchain tarball where you want
to keep libgcc and libc versions when importing it into OE.
regards,
Koen
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
