Hello, I am currently using xapian 1.2.23 with the Search::Xapian perl bindings. I'd like to upgrade to 1.4.0, but it seems that there is no suitable Search::Xapian available, and the SWIG-generated bindings are marked as experimental. So, my question is: Do I have to wait for the new API to get stable, or is there another way for me to upgrade to the 1.4.x branch? I'd like to avoid to adapt to an unstable/experimental API, because Search::Xapian is highly integrated in our system, and the transition involves a lot of effort. Regards, mrks
On Mon, Sep 05, 2016 at 01:51:26PM +0200, Markus W?rle wrote:> I am currently using xapian 1.2.23 with the Search::Xapian perl > bindings. I'd like to upgrade to 1.4.0, but it seems that there is no > suitable Search::Xapian available, and the SWIG-generated bindings are > marked as experimental. So, my question is: Do I have to wait for the > new API to get stable, or is there another way for me to upgrade to > the 1.4.x branch? > > I'd like to avoid to adapt to an unstable/experimental API, because > Search::Xapian is highly integrated in our system, and the transition > involves a lot of effort.I'm currently thinking we probably need a version of the XS bindings which builds against 1.4.x, to allow for a smoother transition if nothing else (the SWIG-based bindings are unlikely to end up 100% compatible). Probably this would just present the same Perl API as you currently get with 1.2.x, rather than attempting to wrap the 1.4.x C++ API where the two differ. Cheers, Olly
On Mon, Sep 12, 2016 at 05:37:02AM +0100, Olly Betts wrote:> On Mon, Sep 05, 2016 at 01:51:26PM +0200, Markus Wörle wrote: > > I am currently using xapian 1.2.23 with the Search::Xapian perl > > bindings. I'd like to upgrade to 1.4.0, but it seems that there is no > > suitable Search::Xapian available, and the SWIG-generated bindings are > > marked as experimental. So, my question is: Do I have to wait for the > > new API to get stable, or is there another way for me to upgrade to > > the 1.4.x branch? > > > > I'd like to avoid to adapt to an unstable/experimental API, because > > Search::Xapian is highly integrated in our system, and the transition > > involves a lot of effort. > > I'm currently thinking we probably need a version of the XS bindings > which builds against 1.4.x, to allow for a smoother transition if > nothing else (the SWIG-based bindings are unlikely to end up 100% > compatible). > > Probably this would just present the same Perl API as you currently > get with 1.2.x, rather than attempting to wrap the 1.4.x C++ API > where the two differ.Search::Xapian 1.2.24.0 can be built using xapian-core 1.4.0, and provides the same Perl API as when built using 1.2.x. Cheers, Olly