@Olly: Agreed - that's not a situation we want to get into. That's also why we'll kick this off from a PPA so one has to specifically opt in to this and we can put a big fat Caveat Emptor sticker on it.
Then if we can guarantee database- and result set compatibility with vanilla libxapian for non-CJK corpuses we can *consider* it for update in main. And if you object *if* we get to that point I am pretty sure the platform team will listen to you - I don't expect that they enjoy maintaining a broken platform :-)
@Olly: Agreed - that's not a situation we want to get into. That's also why we'll kick this off from a PPA so one has to specifically opt in to this and we can put a big fat Caveat Emptor sticker on it.
Then if we can guarantee database- and result set compatibility with vanilla libxapian for non-CJK corpuses we can *consider* it for update in main. And if you object *if* we get to that point I am pretty sure the platform team will listen to you - I don't expect that they enjoy maintaining a broken platform :-)