question about installing multiple versions of a single library
I am putting this out on the list as I have no idea. Maybe someone else can explain this one.
Scott
Quoted 28 lines
-----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 librarysorry 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-libraryand 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.bbi'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.
rday
Hi Robert,
Quoted 19 lines · Scott M
Quoted 19 lines
-----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 librarysorry 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-libraryand 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
Quoted 4 lines
Quoted 4 lines
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.
To be honest I think this section outlines the use case fairly well. Suggestions on how we could improve the explanation would be welcome though.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 27 lines · Paul Eggleton
Hi Robert,
Quoted 19 lines · Scott M
Quoted 19 lines
-----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 librarysorry 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-libraryand 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.bbQuoted 4 lines
Quoted 4 lines
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.
Quoted 5 lines
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.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
Quoted 29 lines · Robert P. J. Day
Quoted 27 lines · Paul Eggleton
Hi Robert,
Quoted 23 lines · Scott M
Quoted 23 lines
-----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 librarysorry 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-libraryand 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.bbi'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.
Quoted 8 lines
Quoted 5 lines
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.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 41 lines · Gary Thomas
Quoted 40 lines · Robert P. J. Day
Quoted 37 lines · Paul Eggleton
Hi Robert,
Quoted 24 lines · Scott M
Quoted 24 lines
-----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 librarysorry for the interruption, i'm reading dev manual here:
http://www.yoctoproject.org/docs/latest/dev-manual/dev->Quoted 1 line
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.bbQuoted 4 lines
Quoted 4 lines
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.
Quoted 5 lines
Quoted 2 lines
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.
yes, i do feel silly about not having noticed that. go ahead ... rub
it in. :-)
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================