Hey :),
On Tue, Mar 1, 2016 at 11:02 PM, Michael Biebl wrote:
> Hi Carlos
>
> 2016-03-01 19:27 GMT+01:00 Carlos Garnacho :
>> I talked with them (Richard Hipp and Dan Kennedy) through private
>> email. The solutions basically seemed to be:
>> - Including a static sqlite copy wherever fts3_tokeniz
Hi Carlos
2016-03-01 19:27 GMT+01:00 Carlos Garnacho :
> I talked with them (Richard Hipp and Dan Kennedy) through private
> email. The solutions basically seemed to be:
> - Including a static sqlite copy wherever fts3_tokenizer() is needed
> - Using FTS5, which offers a way to customize FTS token
Hey Michael,
On Tue, Mar 1, 2016 at 6:48 PM, Michael Biebl wrote:
> 2016-03-01 18:00 GMT+01:00 Carlos Garnacho :
>> Hi Michael,
>>
>> On Tue, Mar 1, 2016 at 4:52 PM, Michael Biebl wrote:
>>> Hi everyone,
>>>
>>> I just noticed that the new tracker 1.6.2 contains a code copy of
>>> sqlite and no
2016-03-01 18:00 GMT+01:00 Carlos Garnacho :
> Hi Michael,
>
> On Tue, Mar 1, 2016 at 4:52 PM, Michael Biebl wrote:
>> Hi everyone,
>>
>> I just noticed that the new tracker 1.6.2 contains a code copy of
>> sqlite and no longer allows one to use the system sqlite library.
>> This is problematic fo
Hi Michael,
On Tue, Mar 1, 2016 at 4:52 PM, Michael Biebl wrote:
> Hi everyone,
>
> I just noticed that the new tracker 1.6.2 contains a code copy of
> sqlite and no longer allows one to use the system sqlite library.
> This is problematic for various reasons and distros like Debian [1]
> and Fed
Hi everyone,
I just noticed that the new tracker 1.6.2 contains a code copy of
sqlite and no longer allows one to use the system sqlite library.
This is problematic for various reasons and distros like Debian [1]
and Fedora strongly discourage such code copies.
Would it be possible to re-add the
