Pushed a fix in sugar-runner. On 26 March 2013 20:32, Daniel Narvaez <dwnarv...@gmail.com> wrote: > On 26 March 2013 18:51, Gonzalo Odiard <gonz...@laptop.org> wrote: >> Then you say we should run xdg-user-dirs-update at start up >> of every sugar session, right? >> >> Can be a solution, but if possible, I prefer avoid it, >> sugar start up is already slow, adding more stuff, >> not needed in the 99% of the cases is not a good idea. > > It's arguable where it needs to be run, but it must be run somewhere > 100% of the time. It doesn't matter if config is at the default dir or > not. > >> Can we run xdg-users-dirs in sugar-build? > > I spent some more time investigating it and I think the right solution > is to add it to sugar-runner. > > There are really two scripts. > > 1 xdg-user-dirs-update. It generates user-dirs.* and it's run by the > display manager (gdm, olpc-dm etc). In Fedora and in Debian it's done > with a xinitrc.d script, but I assume other distributions will have > something similar. > 2 xdg-user-dirs-gtk-update. Tracks locale changes and creates gtk > bookmarks file. It's part of the xdg-users-dirs-gtk GNOME module and > it's run by gnome-session (through xdg autostart). > > Now, in a sugar-build tree, display manager stuff is handled by > sugar-runner, so I think that's where we should run > xdg-user-dirs-update. > > If we care about locale changes, then we should also run > xdg-user-dirs-gtk-update in sugar, but that's a different issue > anyway.
-- Daniel Narvaez _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel