Samuel Thibault, le Sun 17 Oct 2010 16:16:11 +0200, a écrit : > Josselin Mouette, le Sun 17 Oct 2010 14:39:27 +0200, a écrit : > > Le dimanche 17 octobre 2010 à 05:01 +0200, Samuel Thibault a écrit : > > > Josselin Mouette, le Mon 27 Sep 2010 18:20:38 +0200, a écrit : > > > > It shouldn’t be hard to implement with a GConf value that is read in the > > > > greeter. Such a value could easily be set in d-i. > > > > > > How is this done from d-i more precisely? > > > > You need to ship a file in /usr/share/gconf/defaults. Like for gksu, > > this one should probably be an alternative. > > Mmm, ATM there are both speakup and brltty which would want to enable > Orca for instance. How to do this properly? My concern is making sure > that no package upgrade will unexpectedly override the alternative that > has been chosen by d-i. > > Else, a dirty-but-working way would be to let brltty or speakup > d-i scripts create a file in /usr/share/gconf/defaults and run > update-gconf-defaults.
On the debian-boot side, the technical point that bothers me is from where to do it: - from the brltty/speakup packages postinst scripts, but then how they know that they're run from d-i and not just installed on an existing system? (we only want to enable accessibility in gdm automatically when it was enabled at d-i time). - from a finish-install script, but then how to properly run update-gconf-defaults in the target? Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101017201342.gm16...@const.famille.thibault.fr
