2008/4/24 Jamie McCracken <jamiemcc blueyonder co uk>:
On Thu, 2008-04-24 at 15:35 +0200, Mikkel Kamstrup Erlandsen wrote: > 2008/4/24 Jamie McCracken <jamiemcc blueyonder co uk>: > > > > On Thu, 2008-04-24 at 14:51 +0200, Mikkel Kamstrup Erlandsen wrote: > > > > > > > > > > > > Wow, I am delighted to hear this :-) > > > > > > I wont be able to do much until the somewhere early-may. But expect my > > > scrutinizing eye by then :-D > > > > > > Remember that xesam-tools[1] has a few tools to test and query Xesam providers. > > > > > > > hey mikkel, > > > > is it possible for you to get us the full onto in our desktop ini file > > format programatically? > > > > It would be very painful having to do it by hand! > > > > I shall try and get to it tonight. I can put a script for it in > xesam-tools (the framework to it is already there). > > I am a bit busy these days and am going away on holiday sunday, so no > promises :-) > hey no rush - it will be another month or so until xesam support is finished putting it in xesam-tools would rock!
Catch! I have not sanity checked the output, so **please consider this a first stab!** The script is called rdfs2tracker an is in the demo/ directory of xesam-tools bzr trunk. The current Tracker onto contains a lot of extra metadata that is mostly only relevant to the current Tracker client. This needs to be integrated somehow. I propose that we keep that data separate from the clean xesam onto files and then write a script to merge them on install time. That way it will be easier to cope with changes to the xesam onto. Cheers, Mikkel
Attachment:
xesam.metadata
Description: Binary data
Attachment:
xesam.service
Description: Binary data
Attachment:
xesam-convenience.metadata
Description: Binary data
Attachment:
xesam-convenience.service
Description: Binary data
Attachment:
xesam-virtual.metadata
Description: Binary data