Re: Requesting code change after freeze

[Vincent Untz <vuntz gnome org>]

Hi,

Le jeudi 09 mars 2006 �7:25 -0800, Brian Cameron a �it :

[snip]

> 1) The solution I would recommend is to add a new "gdmflexiserver
>     --command" called "GET_CUSTOM_CONFIG_FILE" so that gdmsetup can find
>     out the name of the custom config file that is being used by the
>     daemon.  Then gdmsetup will modify the gdm.conf file and the
>     custom.conf file will be ignored.  The user can choose to migrate
>     (or not) at their leisure.

[snip]

> 2) Perhaps a "nicer" solution would be for GDM to automagically migrate
>     the users gdm.conf settings to the custom.conf file and not use the
>     gdm.conf file at all.  The problem with this approach is that some of
>     the gdm.conf configuration settings (mainly the [server] and
>     [server-foo] sections) are a bit tricky to migrate.  This would make
>     the migration code a bit tricky to implement and perhaps not an
>     appropriate change late in the release cycle.  This sort of migration
>     could be added in the next release if people think that is a good
>     idea.
> 
>     If the release team thinks this is the better approach, I think I
>     can make this work.  I just worry that any bugs in the code would
>     cause the users more issues than doing nothing, and I would be more
>     comfortable adding this sort of logic in 2.15/2.16 than now.

So, here's what I propose: go for solution 1 for 2.14 (consider this as
a private API), and fix it properly in 2.15, removing the private API.

Does it make sense?

Vincent

-- 
Les gens heureux ne sont pas press�