Re: [Tracker] Thunderbird support. Patches for rev. 836



On Thu, 2007-09-13 at 12:52 +0100, Michal Pryc wrote:
jamie wrote:
On Tue, 2007-09-11 at 12:06 +0100, Michal Pryc wrote:
  
Hello Jamie,

I am sending set of patches (patches.836.tar.gz) that adds thunderbird 
support. Those patches are made for revision 836 and contains also fixes 
for Solaris install.

The names and descriptions are the same as in the previous e-mail that I 
  have send to the mailing list, except one file:
thunderbird-extension.diff

which is no more needed, since we've agreed that we will put the 
extension on the tracker svn.

The attached file thunderbird-extension.tar.gz should be uncompressed 
and put into directory trunk/ of tracker svn. If not than the patches 
will break the build, since there will be missing 
thunderbird-extension/Makefile

To build the extension use the flag
./autogen --with-thunderbird-extension

This will generate the tracker.xpi file. I have already made changes, so 
all the strings in the extension are s/beagle/tracker.

    


Hi 

I have added most of this with some changes:


1) I have not added the extension to the tracker folder yet as its
experimental and not finished yet. Once I have ubuntu stuff out of the
way in about 2 weeks and more people have tested it then we can add it
(with beagle filenames removed if possible)
  
Jamie,

We were talking on the IRC about changing strings from beagle to 
tracker. Attached script does this. I have tested that and it works fine.
It need to be run from the ../thunderbird-extension directory (one level 
above thunderbird-extension). I didn't send patch, since it is much 
smaller to send script that do everything.

done and applied - thanks


Also there is small change in the configure.ac, since you have placed 
the extension in the extensions directory, so one check will fail, patch 
attached.

I am also sending build xpi, since it is platform independent (tracker.xpi).

ok where is this installed? (I added it to root of thunderbird-extension
but makefile should specify where it goes for install)


2) I have removed reference to generate makefile in extension. I prefer
the extension to be external for now. Also removed refs from readme.
  
Yes, as we have talked on IRC the best way is to make independant 
makefile/configure from the trunk one.

to be done then (it wont be usable til it is) - I can do the configure
bit if the makefile is complete







[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]