On 2014-08-06 10:20, Robert P. J. Day wrote:
On Wed, 6 Aug 2014, Paul Eggleton wrote:
Hi Robert,
On Monday 04 August 2014 05:29:45 Rifenbark, Scott M wrote:
-----Original Message-----
From: Robert P. J. Day [mailto:[email protected]]
Sent: Sunday, August 03, 2014 2:05 AM
To: Rifenbark, Scott M
Subject: question about installing multiple versions of a single library
sorry for the interruption, i'm reading dev manual here:
http://www.yoctoproject.org/docs/latest/dev-manual/dev->
>manual.html#installing-multiple-versions-of-the-same-library
and the example used (clutter) doesn't even exist in oe-core with those
version numbers, i was looking for another example that actually exists,
didn't immediately see one.
more to the point, the version numbers used in those clutter recipe files
look>
weird:
clutter-1.6_1.6.20.bb
clutter-1.8_1.8.4.bb
i'm not used to seeing recipe files that appear to combine a
higher version number *and* what looks like a minor version
number upgrade as well. do you know what's going on there? maybe
that's not the best example for trying to explain this topic.
The specific versions of clutter may no longer exist in the
metadata, but we do still use this scheme for clutter recipes and
others (gstreamer comes to mind). The point is you change PN to be
version-specific - you have clutter-1.6 and clutter-1.8, such that
you can depend on the specific version where needed.
ah, i see ... the software name is not simply "clutter", it is
"clutter-1.6" or "clutter-1.8". got it.
The '_' in the recipe name is the key - everything to the left of
it is the package name and the version is to the right.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
