Yes, gconf_default_config.patch  was merged to master 
(http://meego.gitorious.org/meegotouch/libmeegotouch/commit/97f0de1baae52e7ab2797a951a3d1643c24ad938).
This patch just sets the default gconf values so it does not crash and works 
with defaults.

However for right behavior it is needed to have right settings. (mainly the 
screen resolution which comes from target name is visible.. )

Nowadays those settings are divided into 2 packages:
1st part (10 from 11 gconf variables) are in meegotouch-handset-configs
2md part (1 variable - /meegotouch/target/name) is in device specific 
configuration package - for example: nokia-n900-configs

So we should ensure that the both configuration packages are installed (in .ks 
files).

BR
Mirek Safr


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Shane Bryan
Sent: 8. lokakuuta 2010 19:15
To: [email protected]
Subject: Re: [meego-packaging] [meego-commits] 8200: Changes to 
devel:qt-mtf/libmeegotouch

On Fri,  8 Oct 2010 08:46:54 -0700 (PDT)
Miroslav Safr <[email protected]> wrote:

> Request #8200:
> 
>   submit:   home:msafr/libmeegotouch(r21) ->
> devel:qt-mtf/libmeegotouch
> 
> 
> Message:
>     * Fri Oct 08 2010 Miroslav Safr <[email protected]>
> 0.20.46-1
> - cleaning removed integrated patches: unit_tests_init.patch,
> gconf_default_config.patch

Has the gconf_default_config.patch been merged upstream?  If not, how
is the device target now specified (or better yet, auto discovered) now?

Regards,

Shane...
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to