Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@openedhand.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/6] 2nd pull request: UX, gtk+/apr, Edwin, Jan19, 2011
Date: Fri, 21 Jan 2011 12:47:13 +0000	[thread overview]
Message-ID: <1295614033.14388.30423.camel@rex> (raw)
In-Reply-To: <1295600248.2382.10.camel@scimitar>

On Fri, 2011-01-21 at 08:57 +0000, Joshua Lock wrote:
> On Fri, 2011-01-21 at 09:21 +0800, Zhai, Edwin wrote:
> > There is also 2.90.X there. And I treated it as development branch, and 
> > stick to lower version.
> > I have compared between 2.22.1 and 2.23.2, and found no much difference. 
> > One case is 2.23.2 support libtool 2.4, but 2.22.1 doesn't, so we may 
> > have some autoconf issue there. Anyway, if you want to stick with stable 
> > version, I can downgrade it to 2.22.1.

Libtool 2.4 support is fine as we autoreconf and it doesn't have to have
it out the box.

For gtk+ we should avoid the 2.90 and 2.odd.x versions so 2.22.1 should
be the version we upgrade to.

If the package report system is saying otherwise, we need to teach it a
bit more about gnome project version numbers! :)

> GNOME version naming should be fairly well documented, version numbers
> are split into x.y.z components.
> The policy is Major.Minor.Release, with an odd minor number indicating a
> development release and an even minor number indicating a stable
> release.
> 
> http://live.gnome.org/ReleasePlanning/ModuleRequirements/Platform
> 
> 2.90.X is the development series for Gtk+3, a major release with no ABI
> guarantee to 2.x - though admittedly this seems to disagree with the
> versioning scheme above.
> If we're going to package 2.90.x it should be in addition to a 2.x
> release, be parallel installable and the recipe be named sufficiently to
> indicate that this is gtk+ 3.
> 
> The 2.23.x unstable branch is towards making a new release of Gtk+ with
> the API/ABI guarantees of the 2.x series for people who are not in a
> position to upgrade to Gtk+3. Most distributions will ship 2 and 3 for
> at least a release or two while non-GNOME software is updated.

Right.

> > > glib: 2.26.1
> > >   
> > 
> > Dongxiao owned this?

Fair enough, we do need to use a stable version of glib-2.0 too though.

> > > eds-dbus: 2.32
> > >   
> > 
> > 
> > My previous upgrade is 2.32.1. But with added nss/nspr, it's rejected. 
> > Working is in progress.

I think Saul confused the message. I dropped the eds-dbus gtk+ related
patch since I didn't take the gtk+ update. I don't think there is a
problem with eds versions but again, we should stick to even release
numbers as its a gnome project.


> > > webkit-gtk 1.2.6
> > >   
> > 
> > Our poky seems never has stable release, and always use development 
> > branch. Maybe we want some new feature? RP can comment. Another benefit 
> > is development branch is under svn, so we can selectively pick some 
> > modules instead of big whole repo. Given development branch, there is no 
> > even/odd difference.
> > 
> > I have a plan to change it to stable release with the cost of long 
> > download & compile time, but I'm afraid can't make it in this release cycle.
> 
> I think we need someone else to own downgrading this recipe for the next
> release then, we can't commit to a 6month stable cycle with an unstable
> software package. Do you have a handle on potential impact of
> downgrading this recipe?
> 
> IIRC only the sato browser (web-webkit) is affected by this recipe?

webkit is an odd beast. My gut instinct says we're better off keeping up
to date with webkit and the 1.3.7 version is ok in this case. I don't
know how "old" 1.2.6 is and how unstable the 1.3 series is though. For
what we use it for (web-webkit), 1.3.7 is probably fine?

Cheers,

Richard



  parent reply	other threads:[~2011-01-21 12:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19  0:46 [PATCH 0/6] 2nd pull request: UX, gtk+/apr, Edwin, Jan19, 2011 Zhai Edwin
2011-01-19  0:46 ` [PATCH 1/6] gtk+: Update to 2.23.2 Zhai Edwin
2011-01-19  0:46 ` [PATCH 2/6] gdk-pixbuf: Add 2.22.1 as new recipe Zhai Edwin
2011-01-19  0:46 ` [PATCH 3/6] eds-dbus: Do not disable old API after upgrading gtk+ Zhai Edwin
2011-01-19  0:46 ` [PATCH 4/6] apr: Update to 1.4.2 Zhai Edwin
2011-01-19  0:46 ` [PATCH 5/6] apr-util: Update to 1.3.10 Zhai Edwin
2011-01-19  0:46 ` [PATCH 6/6] webkit-gtk: upgrade to 1.3.7 Zhai Edwin
2011-01-20 22:49 ` [PATCH 0/6] 2nd pull request: UX, gtk+/apr, Edwin, Jan19, 2011 Saul Wold
2011-01-21  1:21   ` Zhai, Edwin
2011-01-21  1:50     ` Tian, Kevin
2011-01-21  8:36       ` Zhai, Edwin
2011-01-21  8:57     ` Joshua Lock
2011-01-21  9:00       ` Koen Kooi
2011-01-21  9:20         ` Joshua Lock
2011-01-21 12:47       ` Richard Purdie [this message]
2011-01-21 12:58         ` Koen Kooi
2011-01-21 13:42           ` Richard Purdie
2011-01-24  5:04 ` Saul Wold

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=1295614033.14388.30423.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=josh@openedhand.com \
    --cc=poky@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox