From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/12] Recipe upgrades, fixes and additions
Date: Tue, 15 Nov 2011 13:48:11 -0800 [thread overview]
Message-ID: <4EC2DE1B.3070904@linux.intel.com> (raw)
In-Reply-To: <1321393116.26881.229.camel@ted>
On 15/11/11 13:38, Richard Purdie wrote:
> On Tue, 2011-11-15 at 11:03 -0800, Saul Wold wrote:
>> On 11/08/2011 06:18 AM, Richard Purdie wrote:
>>> On Mon, 2011-11-07 at 16:10 -0800, Joshua Lock wrote:
>>>> All,
>>>>
>>>> Here's a series of patches I developed whilst trying to play around with some
>>>> Clutter based software.
>>>>
>>>> The interesting pieces may be:
>>>> Clutter 1.8 series recipes - do we want/need to keep clutter 1.6 around?
>>>> Are we OK with continuing to namespace the clutter recipes by clutter
>>>> version?
>>>
>>> Yes, I think this makes sense.
>>
>> Why do we want to continue the clutter the namespace with version
>> numbers? Was this not for a past issue with mis-matched API/ABI?
>>
>> If that problem is solved, then next remove that version info.
>
> Clutter produces libraries with a very specific namespace so you can
> parallel install clutter 1.4, 1.6 and 1.8. Applications compile against
> a given version of the library.
>
> Having the major lib version as part of the package name therefore makes
> sense. There aren't a lot of projects that do this but this one does and
> it continues to make sense to namespace it accordingly.
With this knowledge "in hand" I've just re-read the 1.8 release notes[1]
and, for better or for worse, this is no longer the case:
"
* This version is API and ABI compatible with the current stable release
of Clutter.
* Installing the contents of this release will overwrite the files from
the installation of the current release of Clutter.
"
For point 1 I'd added a patch to PROVIDES = "clutter-1.6" but I'm not
sure what makes sense in the context of point 2.
Cheers,
Joshua
1.
http://www.clutter-project.org/blogs/archive/2011-09/clutter-1.8.0-stable-release
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-15 21:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 0:10 [PATCH 00/12] Recipe upgrades, fixes and additions Joshua Lock
2011-11-08 0:10 ` [PATCH 01/12] cogl: add cogl 1.8.0 recipe Joshua Lock
2011-11-08 0:10 ` [PATCH 02/12] clutter-1.8: add 1.8.0 Joshua Lock
2011-11-08 0:10 ` [PATCH 03/12] clutter-gst-1.8: add 1.4.2 for use with clutter 1.8 Joshua Lock
2011-11-08 16:10 ` Saul Wold
2011-11-08 16:30 ` Joshua Lock
2011-11-08 16:54 ` Saul Wold
2011-11-08 16:59 ` Joshua Lock
2011-11-08 0:10 ` [PATCH 04/12] clutter-gtk-1.8: add clutter-gtk 0.11.4 Joshua Lock
2011-11-08 0:10 ` [PATCH 05/12] mx: add mx toolkit 1.3.2 Joshua Lock
2011-11-08 0:10 ` [PATCH 06/12] classes/[gnome|gnomebase|mime]: merge meta-oe's enhance gnome related classes Joshua Lock
2011-11-08 14:05 ` Richard Purdie
2011-11-08 16:35 ` Joshua Lock
2011-11-08 0:10 ` [PATCH 07/12] gconf: add upstream GNOME gconf 3.2.3 and drop gconf-dbus Joshua Lock
2011-11-08 0:10 ` [PATCH 08/12] libcanberra: add libvorbis to DEPENDS Joshua Lock
2011-11-08 0:10 ` [PATCH 09/12] gypsy: fix packaging Joshua Lock
2011-11-08 0:10 ` [PATCH 10/12] connman: split scripts into separate package Joshua Lock
2011-11-08 14:17 ` Koen Kooi
2011-11-08 0:10 ` [PATCH 11/12] pulseaudio: make X11 dependencies optional and add gtk+ Joshua Lock
2011-11-08 0:10 ` [PATCH 12/12] contacts: fix packaging of icons Joshua Lock
2011-11-08 14:18 ` [PATCH 00/12] Recipe upgrades, fixes and additions Richard Purdie
2011-11-08 15:48 ` Saul Wold
2011-11-15 19:03 ` Saul Wold
2011-11-15 21:38 ` Richard Purdie
2011-11-15 21:48 ` Joshua Lock [this message]
2011-11-08 17:36 ` Saul Wold
2011-11-08 18:31 ` Joshua Lock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EC2DE1B.3070904@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.