Closed kingfisher77 closed 2 years ago
Dovecot version in Bullseye container ist 2.3.18:
deb http://repo.dovecot.org/ce-2.3.18/debian/bullseye bullseye main
We compile the module and copy it to Dovecot (/usr/lib/dovecot/modules) which is a dovecot bullseye repo install in a bullseye container.
You have to run the module against a Dovecot core that contains all necessary libraries (stemmer/textcat/icu). The "standard" Dovecot packages do not provide this. (This is why we have to do the expensive build step of compiling Dovecot every time we do github CI - since you can't compile/execute against a generic installable Dovecot package.)
This compilation difficulty goes away in the (forthcoming) CE 2.4, where flatcurve is built-in to Dovecot core.
Thank you for explaining again. We were expecting that copying the plugin file from a same environment would be sufficient. But it is logical - if libraries are not present, it cannot work.
We compiled now dovecot with flatcurve and all features needed by ourselve. Full text search is running like hell! :-) Thank you for your awesome work.
FWIW, I believe it would be possible (with some degree of unknown efforts) to have the plugin code directly link to the libraries, so you could perform what you originally attempted to do.
The focus of this project was to create an FTS plugin that was eventually going to be incorporated into core Dovecot code, so it made sense to use the existing compilation/linking framework in Dovecot to handle these libraries (and this compilation code tends to be a bit fragile, so best not to touch unless you have to).
However, at this point, the code in this repository is being maintained for use with 2.3 until the next version of CE is coming out. My opinion is that I don't want to make drastic changes at this time since the code is working (mostly) stable for people, albeit with a bit of compilation dependencies necessary to get it to work.
BTW Do you know approximately when version 2.4 will be released?
There is no date, unfortunately.
We cannot get rid of this message using compiled dovecot-fts-flatcurve:
We looked at this and this issue.
We compile the module and copy it to Dovecot (/usr/lib/dovecot/modules) which is a dovecot bullseye repo install in a bullseye container.
What is wrong with us? ;-)
Our environment is this:
Dockerfile: .github/actions/dovecot-fts-flatcurve-test/Dockerfile