Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading libgtk2 and libglibg2 to latest	versionbefore the	release?
Date: Sat, 17 Jan 2009 18:29:51 +0100	[thread overview]
Message-ID: <1232213391.20691.13.camel@bender> (raw)
In-Reply-To: <87ocy53nor.fsf@macbook.be.48ers.dk>

Hi,

On Sat, 2009-01-17 at 17:24 +0100, Peter Korsgaard wrote:

> Or simply leave it as it is for now. Do we have any concrete reason
> for upgrading the gtk version? I'm using gtk 2.12 on my Debian machine
> as well. The bug tracker issue was for glib, and there's afaik no
> issues with using a newer glib version with gtk 2.12 (I'm having 2.16
> here).

I have been running gtk+ 2.12 together with glib 2.18 for several months
on my desktop machine. glib 2.18 is fully backward compatible with
earlier glib 2.x releases and afaik there are no known
incompatibilities. As I am also following the gtk-devel list, I would
probably know if there were any.


Sven

      reply	other threads:[~2009-01-17 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 22:16 [Buildroot] Upgrading libgtk2 and libglibg2 to latest version before the release? Ulf Samuelsson
2009-01-17  6:46 ` Peter Korsgaard
2009-01-17 17:25   ` Sven Neumann
2009-01-17 17:49     ` Peter Korsgaard
2009-01-17  6:50 ` Peter Korsgaard
2009-01-17  8:06 ` [Buildroot] Upgrading libgtk2 and libglibg2 to latest versionbefore " danieljlaird at hotmail.com
2009-01-17 16:24   ` Peter Korsgaard
2009-01-17 17:29     ` Sven Neumann [this message]

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=1232213391.20691.13.camel@bender \
    --to=s.neumann@phase-zero.de \
    --cc=buildroot@busybox.net \
    /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