All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][v2] clutter: Bump revisions to latest stable & cleanup
Date: Tue, 31 Aug 2010 18:15:46 +0200	[thread overview]
Message-ID: <i5j9ri$ie9$1@dough.gmane.org> (raw)
In-Reply-To: <201008311641.00363.schnitzeltony@gmx.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31-08-10 16:41, Andreas Mueller wrote:
> On Tuesday 31 August 2010 10:36:01 am Koen Kooi wrote:
>> It is used to seperate the clutter api/abi change. 0.8 is parallel
>> installable with 1.0 (0.9 is 1.0rc), so the naming is there to support
>> both kinds of clutter.
>> What I wanted to do, but didn't find time for:
>>
>> 1) name the clutter 0.8 series clutter-*-0.8
>> 2) name the post 0.8 series clutter-*
>>
>> That should be safe to do since clutter 1.2 is supposed to be compatible
>> with 1.0.
> I would like to take care for this. Before I dive into it how about this schedule:
> 
> 1. remove very old recipes: clutter*svn*.  As far as I saw are the o-hand svn-sources for clutter no more available. Replace DEPENDS on clutter-cairo to clutter & cairo.
> 
> 2a. all recipes with v >=0.9 rename to clutter*_v
> 2b. all recipes with v < 0.9 rename to clutter-*-0.8
> 2c. recipes depending on clutter*: Those depending on v >= 0.9 will get DEPENDS on clutter* / those depending on v < 0.9 ( think it will only be recipes/gnome/libchamplain-gtk_0.2.8.bb ) get 
> DEPENDS on clutter*-0.8 ( maybe this can be changed later to clutter* )
> 
> 3. Add the recipes I made for latest stable versions
> 
> What do you think?

Sound like a good plan! FWIW, I think we should only keep 0.8.x, 1.0.x
and 1.2.x (1.0 and 1.2 should be compatible) to have a complete set to
compare things, the GLES engines tend to break from release to release,
so keeping a handfull of versions around is good practice.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMfSqyMkyGM64RGpERAgvqAJ9Swj/3YLsRb/DHmQfX9BpqT/OQYQCfVFfh
TxNfP9aLw209Lm/5KsMYeIw=
=lqGG
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-08-31 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 13:56 [PATCH2/2][v2] clutter: Bump revisions to latest stable & cleanup Andreas Mueller
2010-08-30 16:16 ` [PATCH][v2] " Andreas Mueller
2010-08-31  8:36   ` Koen Kooi
2010-08-31 14:41     ` Andreas Mueller
2010-08-31 16:15       ` Koen Kooi [this message]
2010-09-03  0:48         ` Andreas Mueller

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='i5j9ri$ie9$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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.