[maemo-developers] [maemo-developers] gtk+ and gnome-vfs, upstreamable or a fork?

[From: Koen Kooi]

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

Devesh.Kothari at nokia.com wrote:
> idea is to move and merge as much as possible to mainstream, but for some changes it might be easy and some difficult, so this is a goal but IMHO would not happen for some time, especially some of the changes might make sense only for the embedded devices UI and hildon in particular and more difficult to pass and accepted in mainstream.

We have the same "problem" in GPE as we modify gtk for a better
stylus-behaviour too, but there's at least one osso reference in the
maemo-gtk. It built fine without it, so it might be an unintended
addition. I'll try maemo with a stock gtk 2.6.7 when I have some time.
Thanks for the answers.

regards,

Koen
> Devesh
> 
> 
> 
>>-----Original Message-----
>>From: maemo-developers-bounces at maemo.org
>>[mailto:maemo-developers-bounces at maemo.org]On Behalf Of ext Koen Kooi
>>Sent: 31 May, 2005 15:57
>>To: maemo-developers at maemo.org
>>Subject: [maemo-developers] gtk+ and gnome-vfs, upstreamable 
>>or a fork?
>>
>>
>>Hello,
>>
>>After poking through the patches, it seems both the gtk+ and gnome-vfs
>>found in the repository require some incarnation of osso. I would like
>>to use maemo apps on my Sharp Zaurus with a stock gtk+ and
>>gnome-vfs-dbus, but that's not possible at the moment.
>>Is it planned to clean up gtk+ and gnome-vfs, get patches 
>>into upstream
>>and use stock versions in later maemo releases, or will you 
>>effectively
>>fork gtk+ and gnome-vfs?
>>
>>regards,
>>
>>Koen
>>
>>_______________________________________________
>>maemo-developers mailing list
>>maemo-developers at maemo.org
>>https://maemo.org/mailman/listinfo/maemo-developers
>>
> 
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
> 

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

iD8DBQFCnbqoMkyGM64RGpERAi+sAJ4j5guIMph8zAz/WhF3Ois0qoNt/gCgjBAR
MWCFkKPTq/U9Xva3R1FgVe0=
=yJNw
-----END PGP SIGNATURE-----