[FTS Xapian] Beta release

[Joan Moreau]

Ok for having a link on the FTS page. 

PLease clarify what files are necessary to package it as a separate
package

On 2019-01-13 19:03, Aki Tuomi wrote:

> Yes, from compiling point of view it is done.
> 
> Unfortunately what is not done is all the other work involved, such as fixing all the inevitable bugs it has and maintaining it. We do not want, at this moment, take up maintaining and developing yet another FTS plugin as we have plenty of things to do already.
> 
> I invite you to setup your own repository and provide this plugin from there, being the maintainer of this plugin. We can add a link to your plugin on our FTS page so people can also find it.
> 
> There are other plugins like this, e.g. https://github.com/st3fan/dovecot-xaps-plugin
> 
> Aki
> 
> On 13 January 2019 at 19:52 Joan Moreau <jom at grosjo.net> wrote:
> 
> The only point here of this fts-xapian is to get rid of solr (because it
> is just a nightmare to setup) and squat (because it is considere
> obsolete). 
> 
> I already sent the changed in configure.ac, makefile.am, etc.. in order
> to include it in the dovecot, and it compiles properly 
> 
> The only remaining point is to push it in hte git (yes, everything is
> already done) 
> 
> On 2019-01-13 18:45, Aki Tuomi wrote:
> 
> On 13 January 2019 at 17:05 Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
> 
> Hi 
> 
> Please find attached the beta release of FTS Xapian, with the objective
> to replace fts_squat that is being deprecated. 
> 
> Configuration is exactly the same as for fts_squat: 
> 
> plugin { 
> 
> plugin = fts fts_xapian (...)
> fts = xapian
> fts_autoindex = yes
> fts_enforced = yes
> fts_xapian = partial=2 full=20 
> 
> This is installed on my production server (>120Gb of mailboxes), and I
> will observe it during the coming days. 
> 
> I will definitely appreciate that this is added in the core git of
> docevot, in order to have a versionning of it, to remove squat and let
> basic users able to avoid Solr alternative as much as possible. 
> 
> Thanks 
> 
> JM 
> Hi!
> 
> I still recommend you setup a, say, github repository for your plugin. We are not able to currently include your work in dovecot core as it is more work than just pushing the code into the repo. Maybe it can be included in the future.
> 
> If you want, I can help you in setting up the required configuration scripts and such to make it possible to compile it as plugin.
> 
> Then anyone can download it and install it for their dovecot, even if dovecot itself has been installed from packages, and also makes it possible for package maintainers to consider including it in distributions.
> 
> Aki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20190113/1039d20d/attachment-0001.html>