On Thu, May 22, 2008 at 12:46 PM, Ivan Frade <[EMAIL PROTECTED]> wrote: > Hi Tshepang, all > > El jue, 22-05-2008 a las 12:21 +0200, ext Tshepang Lekhonkhobe escribió: >> Hi, >> >> Is there any reason why TP is using its own config library instead of >> src/libtracker-common/tracker-config.[ch] or does it just need some >> work? >> > > I think it is just a questions of put some work. Both tracker-config > and tracker-configuration can write the tracker.cfg file! > > > At some point, we must put some order in the configuration options. We > must choose what options are available, which ones requires to restart > the daemon, and which ones can change in runtime. > > My idea is that trackerd should load the options from the config file, > and write the options when it finish (for example). In the middle, TP > can read/write the values of the options using a DBus Interface. The > daemon could also throw a signal saying "Some option have changed!" and > TP can ask again the values of the options.
Good ideas... > Definetly, TP shouldn't read/write directly the cfg file. ...especially because their cfg files don't look the same, even down to the names of the config options (EG EnableFastMerges vs. FastMerges)! -- my place on the web: floss-and-misc.blogspot.com _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
