Raphael Hertzog, le Fri 19 Apr 2013 08:48:58 +0200, a écrit : > Now you're calling dbus-launch and I expect that a side-effect of this > is to create /var/lib/dbus/machine-id.
Ok. > (it might not be a big deal, but it's the kind of side effect that I prefer > to avoid) Sure. > > > 3/ you change directly the user configuration instead of adjusting > > > the defaults (this one is debatable since supplementary users might > > > not want a11y enabled by default but this is a minor inconvenience) > > > > Yes, thus Cc-ing debian-accessibility. I'm not sure what we really > > want. Most often, users (other than the person who installed the system > > with braille or speech) will not want accessibility being enabled. > > Yeah, but how common is the multiple users per machine scenario ? Well, the home computer, typically. > And whatever happens, all users will have gdm with a11y enabled. Yes, that is not an issue. Logging into gdm is not very talkative anyway. > > On the other hand, just changing the default could be less surprising > > than having a configured user. > > > > But on the other hand again, having "a file in > > /usr/share/glib-2.0/schemas outside of dpkg's knowledge" is not a good > > thing either, and people will wonder how this script ended up there, and > > not coming from a package. > > That's why I have put a clear comment on the top of the file that says > what created this file. I agree it's not perfect but the same goes for having > one user pre-configured and not the others... Right. > The other positive point of changing the default is that you don't have > to special case and hardcode the knowledge of the gdm user. Indeed. > > > 4/ if the system is reconfigured so that gsettings uses something else > > > than dconf as backend, > > > > Urgl, so gsettings might be storing parameters another way, depending on > > the system preference? That, however is really a problem indeed. > > Yes. That said I don't know anyone who has done it in production. The only > supported databases so far are dconf and gconf. Ok. > > Would it be possible to store a schema file somewhere in the user home? > > Not that I know. Too bad. > > Now, an issue is that while finish-install can be updated with a new > > patch without rebuilding debian-installer, brltty can not, and rc2, > > supposed to be used for 7.0.0, is already on its way. Ideally we'd use > > the same strategy for both the speakup and the brltty installations... > > Yes, I agree. That said it doesn't break anything to mix up the strategies. > Thus we can always sync for 7.0.1. Right. So I'd say we can go with your version, and we'll make brltty switch to that with 7.0.1. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
