On 10/05/14 01:55, Michael Biebl wrote:
I noticed that
/usr/include/tracker-1.0/libtracker-control/tracker-miner-manager.h
includes the following warning
#if !defined (__LIBTRACKER_CONTROL_H_INSIDE__) && !defined
(TRACKER_COMPILATION)
#error "Only can be included directly."
#endif
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Biebl schreef op 9/05/2014 23:18:
[cut]
> While we are at it: In the Debian tracker package I currently use
> --with-enca (or now --enable-enca) and libunistring for UTF-8
> support.
>
> Is that a reasonable choice or would you suggest to us
I noticed that
/usr/include/tracker-1.0/libtracker-control/tracker-miner-manager.h
includes the following warning
#if !defined (__LIBTRACKER_CONTROL_H_INSIDE__) && !defined
(TRACKER_COMPILATION)
#error "Only can be included directly."
#endif
I suppose that should be
#if !defined (__LI
2014-05-09 22:12 GMT+02:00 Philip Van Hoof :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Kalev Lember schreef op 9/05/2014 13:17:
>> On 05/09/2014 11:06 AM, Martyn Russell wrote:
>>> * build: Switch --with-enca is now --enable-enca * build: Switch
>>> --enable-icu-charset-detection has be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kalev Lember schreef op 9/05/2014 13:17:
> On 05/09/2014 11:06 AM, Martyn Russell wrote:
>> * build: Switch --with-enca is now --enable-enca * build: Switch
>> --enable-icu-charset-detection has been added to prefer ICU over
>> enca for MP3 content det
On 05/09/2014 11:06 AM, Martyn Russell wrote:
> * build: Switch --with-enca is now --enable-enca
> * build: Switch --enable-icu-charset-detection has been added to
> prefer ICU over enca for MP3 content detection
Which one should we use in distro builds (Fedora)?
--
Kalev
___
About Tracker
=
Tracker is a semantic data storage for desktop and mobile devices.
Tracker uses W3C standards for RDF ontologies using Nepomuk with
SPARQL to query and update the data.
Tracker is a central repository of user information, that provides two
big benefits for the user; s
