better example than "clutter" for multiple versions of same lib?

better example than "clutter" for multiple versions of same lib?

[Robert P. J. Day]

  in current dev manual, "5.5.3. Installing Multiple Versions of the
Same Library", one reads:

"As an example, the following two recipes would allow the two
separate versions of the clutter library to co-exist on the same
system:

     clutter-1.6_1.6.20.bb
     clutter-1.8_1.8.4.bb

  given that those recipes don't even exist (and i have no idea what
that numbering scheme is supposed to represent), can anyone point out
a better example to use for that section?

  i have a tweak or two for that chapter, so i might as well do it all
at once, if someone can suggest a better recipe for the above.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: better example than "clutter" for multiple versions of same lib?

[Khem Raj]

On Mon, Aug 4, 2014 at 10:26 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
>   in current dev manual, "5.5.3. Installing Multiple Versions of the
> Same Library", one reads:
>
> "As an example, the following two recipes would allow the two
> separate versions of the clutter library to co-exist on the same
> system:
>
>      clutter-1.6_1.6.20.bb
>      clutter-1.8_1.8.4.bb
>
>   given that those recipes don't even exist (and i have no idea what
> that numbering scheme is supposed to represent), can anyone point out
> a better example to use for that section?

when you need to have two versions of same library which are ABI
incompatible then you rename the recipes to solve the namespace
violations.
may be use libusb as example if clutter is gone.