GLib package update (2.22 and 2.26)
 

Just when I thought I was out, Google pulled me back in.

I got frustrated that Google broke GTalk Voice/Video with our phones and I've started a quest to fix it.

First off: GLib provided in Maemo 5 is ancient. I've managed to build a new package set that works on my N900 (and all the apps). I have built 2.22 and 2.26. 2.22 introduces GIOStream stuff, but the version of telepathy-gabble (what is used for GTalk) that works with the new GTalk V/V protocol requires 2.26. Google searches found previous requests for updated Glib packages, but no one seemed to be successful until today.

I will provide the source and binary packages for GLib today. Unfortunately when I tried the updated telepathy packages I could no longer connect to GTalk at all so there is no point in linking to them just yet. These packages should be backwards compatible with all Maemo 5 software as no major ABI removals were made - just major additions.

The glib2 work was copied from this abandoned git repo on gitorious: http://maemo.gitorious.org/maemo-gno...ib/trees/maemo. I had to apply the Nokia glib2 patches and debian rules files to get a working package.

GLib 2.22.4
Binary package: http://www.4shared.com/file/FSHo1hJL...mo0_armel.html
Data package (optional): http://www.4shared.com/file/ZuI8dzt3...maemo0_al.html
Dev package: http://www.4shared.com/file/LoZV9ZPN...aemo0_arm.html
Debug package: http://www.4shared.com/file/bF6z75fh...2maemo0_a.html
Source package1: http://www.4shared.com/file/zkG-Ah_E...mo0_armel.html
Source package2: http://www.4shared.com/archive/9x3wn...maemo0tar.html
Source package3: http://www.4shared.com/file/37k5eUDj...4-2maemo0.html

GLib 2.26.0
Binary package: http://www.4shared.com/file/7zI32x9L...mo2_armel.html
Data package (optional): http://www.4shared.com/file/I3mjRJwH...maemo2_al.html
Dev package: http://www.4shared.com/file/bdM5Ym80...aemo2_arm.html
Debug package: http://www.4shared.com/file/WBGSwN6D...0maemo2_a.html
Source package1: http://www.4shared.com/file/nV99R6ot...mo2_armel.html
Source package2: http://www.4shared.com/archive/soZTd...maemo2tar.html
Source package3: http://www.4shared.com/file/z6s58ZDN...0-0maemo2.html

PLEASE READ -- Replacing glib2 may require you to reflash the rootfs (wiping out all your apps) if something goes wrong. PLEASE BACKUP BEFORE INSTALLING.

TWEAKERS PLEASE READ - This will not provide you a speed boost. More likely it will eat a bit more RAM (the libs are a few hundred kilobytes larger than glib2 2.20). These packages are for developers who need to be able to bring updated apps to Maemo 5.

Re: GLib package update (2.22 and 2.26)
 

This seems really promising for porting new applications, for example latest version of MyPaint. , Are you planning to push this update (once tested) to CSSU?

Re: GLib package update (2.22 and 2.26)
 

What would be the best way to get glib 2.26 into the CSSU?

I'm by no means an expert debian packager so I may need someone to look over how I packaged this and fix any mistakes. I come from RPM based distros where I am a Fedora packager.

Re: GLib package update (2.22 and 2.26)
 

you can try uploading to extras-devel (maybe 2.22?). You tested it on your device, didn't you?

Re: GLib package update (2.22 and 2.26)
 

Be careful, if you upload GLib to Extras with the same name than the original package, that would enable an upgrade for anyone using apt-get upgrade.

You might also want to check these thread:
- gcc-4.6 and Fremantle, WIP
- studies about newer libglib on fremantle
and contact with AapoRantalainen

Re: GLib package update (2.22 and 2.26)
 

Unless the anyone uses apt-pinning. Isn't extras-devel meant to brick devices? :DD
By the way, is it possible to specify something in debian/control so that user has to specify additional parameter to install such package (as it's with debian backports)?

But it shouldn't be uploaded without testing, indeed.

Re: GLib package update (2.22 and 2.26)
 

Is this version 2.26 tested on device?

As written earlier I have made some testing and bricked/flashed device several times. So I'm very curious about this, but can't flash device at this moment.

----
If 2.26 is working, is there any show stoppers for 2.33?

Release dates:

Re: GLib package update (2.22 and 2.26)
 

Glib 2.26 is tested on my device (latest CSSU-thumb, kp51)

Now, let's try 2.33!

Re: GLib package update (2.22 and 2.26)
 

I tested Glib 2.26 with fresh-flashed PR-1.3 and didn't find any problem.

Re: GLib package update (2.22 and 2.26)
 

Is there any reason to use Glib 2.22 rather than 2.26?