Newer glib on Maemo5

Hello!

I have an application I am trying to port to Maemo 5 that requires a
newer version of libglib2.0 (2.22) than what is on the device (2.16).
Does anybody know what horrible things might happen if I brute-force a
2.22 (and its newer dependencies) on the device? Is there anyway
around this problem (perhaps some kind of copy on write chroot with a
symlinked version of everything but glib and co?)?

Thanks,
Zach

On Tuesday 17 November 2009 16:08:57 Zachary Goldberg wrote:
> 2.22 (and its newer dependencies) on the device? Is there anyway
> around this problem (perhaps some kind of copy on write chroot with a
> symlinked version of everything but glib and co?)?

I would also suggest checking first if the application *really* needs that
version of libglib. It's not uncommon that the version specified is the
lowest version that the application has been tested with, not the lowest
version that will actually work with.

El mar, 17-11-2009 a las 10:08 -0500, Zachary Goldberg escribió:
> Hello!
>
> I have an application I am trying to port to Maemo 5 that requires a
> newer version of libglib2.0 (2.22) than what is on the device (2.16).
> Does anybody know what horrible things might happen if I brute-force a
> 2.22 (and its newer dependencies) on the device? Is there anyway
> around this problem (perhaps some kind of copy on write chroot with a
> symlinked version of everything but glib and co?)?

Maemo 5 currently has glib 2.20 (2.20.3-1maemo3). In theory, upgrading
to glib 2.22 shouldn't be a problem, but I am not aware of any plans to
do it at this stage.

If you want to experiment, you can get the debian packaging bits from

https://stage.maemo.org/svn/maemo/projects/haf/trunk/glib/

and build a glib 2.22 starting from that.

Claudio

Zachary Goldberg ha scritto:

> I have an application I am trying to port to Maemo 5 that requires a
> newer version of libglib2.0 (2.22) than what is on the device (2.16).
> Does anybody know what horrible things might happen if I brute-force a
> 2.22 (and its newer dependencies) on the device?

Speaking as an expert ;-) on the topic of "bad things" that can happen
when overriding a core library, I would try either relaxing the
dependency (if possible) or statically linking just that library.

A.