On Mon, May 21, 2007 at 12:32:52PM -0700, Adam Zimmerman wrote: > On Mon, 2007-21-05 at 16:30 +0100, Peter Robinson wrote: > > > > > Any chance of a 0.10.1 release with the current work before it gets > > > > > the dependency on glib 2.14? > > > > > > > > We won't be adding a dependency on glib 2.14. We'll just use the new > > > > timeout function if glib 2.14 is available at ./configure time. > > > > > > How would that work for python plugins like the Magnatune one (which > > > uses timeouts to decide when to check for a new version of the catalog)? > > > > What sort of times are we talking about? Surely you don't check for > > new versions of the catalog on a sub second basis? That call is > > designed for things that don't need sub second accuracy so the wakeups > > can happen every second. So if you do it by seconds and at a guess it > > wouldn't matter if the update ran a bit early or late for something > > like a catalog update. > > Yeah, the update is every six hours, accuracy isn't that important. I > was actually asking about the "checking the dependency at compile time" > part. Sorry if that wasn't clear. As far as I know, you can't do that > easily with python plugins. I was wondering if that would mean we'd have > to add code to the plugin to decide whether to use the new call or not, > and how that would work.
I haven't looked at that yet, but I think we can probably add a wrapper method in the 'rb' python module that figures out if gobject.timeout_add_seconds is available, equivalent to the 'rb_timeout_add_seconds' #define that my current patch uses. _______________________________________________ rhythmbox-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
