summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Release 2.1.12.1.1Carlos Garnacho2018-08-011-1/+1
|
* Release 2.1.02.1.0Carlos Garnacho2018-07-231-2/+2
| | | | | | Supersedes 2.0.5 (to be ignored). The previous release introduced new API to let TrackerResource output JSON-LD, so this warrants a minor version bump as per semantic versioning.
* Release 2.0.52.0.5Carlos Garnacho2018-07-221-1/+1
|
* functional-tests: Autotools now runs functional tests against source treeSam Thursfield2018-07-161-2/+2
| | | | This is how Meson already behaves.
* Add support to TrackerResource for outputting metadata as JSON-LDsam/resource-jsonldSam Thursfield2018-07-151-2/+3
| | | | | This also adds `tracker extract -o json` to dump resources in JSON-LD, in anticipation of corresponding updates in tracker-miners.git.
* Release 2.0.42.0.4Carlos Garnacho2018-06-251-1/+1
|
* build: Bump sqlite3 dependencysqlite-depErnestas Kulik2018-06-101-1/+2
| | | | SQLITE_DETERMINISTIC was introduced in 3.8.3.
* Release 2.0.32.0.3Carlos Garnacho2018-02-071-1/+1
|
* configure: Don't put includes in function body of AC_LANG_PROGRAMTing-Wei Lan2018-01-241-2/+2
| | | | | | | | | The second argument of AC_LANG_PROGRAM is the content of main function. We cannot put any includes there, or we end up testing whether the compiler supports nested functions because headers may have definitions for inline functions. https://bugzilla.gnome.org/show_bug.cgi?id=792713
* functional-tests: Fix configuration to work with MesonSam Thursfield2017-12-181-1/+4
| | | | | | | | | | | | | | | | | | | | | | Previously the functional-test suite would test the installed version of Tracker, but would need to be run from a configured Tracker source+build tree. I have changed how things are configured and now with Meson the functional tests can be run completely from the build tree, without needing to install anything. The Autotools `make functional-test` target works the same as before. Instead of generating a Python source file that contains the build-time configuration, we write that to a .json file which is read when the common.utils.configuration module is imported. This controls the locations of the various things that the tests require, which allows us to avoid hardcoding knowledge of the build tree layout into the tests themselves. With the new setup it should also be possible to add a target that explicitly installs the functional tests, with a different configuration.json file so that they test the installed version of Tracker. That's not yet implemented.
* functional-tests: Remove tests that belong in tracker-miners.gitSam Thursfield2017-12-181-1/+0
|
* Remove leftover hal bitsMichael Biebl2017-11-151-39/+0
| | | | Those are no longer used after the tracker-miners split.
* Release 2.0.22.0.2Carlos Garnacho2017-11-141-1/+1
|
* Release 2.0.12.0.1Carlos Garnacho2017-10-041-1/+1
|
* Release 2.0.02.0.0Carlos Garnacho2017-09-121-3/+3
| | | | Semantic versioning is now effective.
* build: Drop obsolete _REQUIRED versionsMichael Biebl2017-08-311-21/+0
|
* build: Drop obsolete warning about seccompMichael Biebl2017-08-311-6/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=787057
* Release 1.99.31.99.3Carlos Garnacho2017-08-221-1/+1
|
* build: Mandate that sqlite3 >= 3.20.0 has fts5 builtinCarlos Garnacho2017-08-221-0/+7
| | | | | | | | | | | | | | | That sqlite3 version brought incompatibilities in the fts5 interface, fts5 modules generated from < 3.20.0 trees won't work with sqlite3 >= 3.20.0, and viceversa. Since it's not feasible nor desirable to include an additional fts5 module copy nor an embedded sqlite3 amalgamation copy, mandate that SQLite was compiled with --enable-fts5 if >= 3.20.0 is found. The current copy of the fts5 module is kept around for sqlite3 < 3.20.0, so we don't make this a mandatory requirement for earlier versions. https://bugzilla.gnome.org/show_bug.cgi?id=785883
* Release 1.99.21.99.2Carlos Garnacho2017-08-071-1/+1
|
* Remove all miners/extract/writebackCarlos Garnacho2017-08-031-1288/+0
| | | | This is being split to its own package
* libtracker-miner: port to libnmLubomir Rintel2017-07-241-3/+3
| | | | | | | | It's the perferred NetworkManager's library for a couple of years now already. Keep compatibility with the older one, since it's reasonably similar. https://bugzilla.gnome.org/show_bug.cgi?id=777178
* Release 1.99.11.99.1Carlos Garnacho2017-07-191-1/+1
|
* configure: Do not generate src/plugins/MakefileCarlos Garnacho2017-07-031-1/+0
| | | | Makefile.am is not there anymore.
* utils: Remove gtk-sparql utilCarlos Garnacho2017-07-031-1/+0
| | | | | It's not even ported to pygi, it could go to examples/ if refurbished, but there's aplenty on internet.
* Delete tracker-needleCarlos Garnacho2017-07-031-51/+0
| | | | | | | | | | | | | It was cool when Tracker search was barely integrated anywhere. Nowadays, it's nothing but an aging showcase app (eg. was conceived in the gtk2 days and barely ported to gtk3, and it shows everywhere). If you want a modern and capable search UI, try Nautilus. If you are outraged that tracker-needle is gone and ended up here, by all means be my guest, reset to the parent of this commit and take it out of tree. If you join #tracker I'll gladly give you advise on how could it be brought up-to-date. But our hands are full, sorry, we leave cool UIs to others.
* Delete tracker-preferencesCarlos Garnacho2017-07-031-41/+0
| | | | | | | | | | | | | | This is a mix of store and miner features which can't be assumed to go together. It is better to leave configuration UI up to the environment, in the GNOME case this is gnome-control-center search panel. For settings that fall in the cracks, or for environments that don't integrate Tracker search in their configuration UI, there's the rather capable dconf-editor which will provide all toggles, and will explain them better than any UI we may have. In the future the CLI tools might gain some configuration subcommand, but it will not be a graphical UI.
* Delete evolution/thunderbird/nautilus/firefox pluginsCarlos Garnacho2017-07-031-301/+0
| | | | | | | | | | | | | | Those are unmaintained, are broken, don't compile, or a combination of all. Sadly there hasn't been enough manpower during the last years to keep those up to par. Future seems shiny enough for nautilus, as the features are being developed in-tree. If anyone ever remembers there were such plugins and misses them enough to take over maintainership, by all means reset to the parent of this commit and take those out of tree. You will have my gratitude. Thanks too to everyone who ever contributed in those plugins, I'm not happy to let that much work go.
* Remove libmediaart code entirelyCarlos Garnacho2017-06-291-49/+0
| | | | | The libmediaart dependency was disabled in commit 6a05068624bfa, it doesn't make sense to drag this code around.
* ontologies: Build dc/xsd/rdf/nrl/nao as GResourceCarlos Garnacho2017-06-281-0/+3
| | | | | | | | | | | Those ontology files are the tracker core, as the database files' structure is modeled around those classes and properties. Include those as a GResource so they're guaranteed to be there, all other ontology files are optional and must be provided on TrackerDataManager initialization. The NAO ontology has been split between the official bits (included in the GResource) and the non-official bits (just used by the evolution miner, and moved to 90-tracker)
* configure: Bump API versionCarlos Garnacho2017-06-281-2/+2
|
* autotools: Don't set -Wl,--enable-new-dtags globallyCarlos Garnacho2017-06-281-1/+3
| | | | | | | Just set it in library LDFLAGS, otherwise introspection may find the installed libraries before the ones being built, which is not the right thing if there are new symbols/types to be looked up.
* Remove Maemo/Meego leftoversSam Thursfield2017-06-081-90/+1
| | | | | | | | | | | | | | | | | | | This removes various code paths that we believe to be unused. * The userguides miner has been removed altogether. * The application miner no longer parses MeeGo-style .desktop files * The TRACKER_DISABLE_MEEGOTOUCH_LOCALE environment flag is gone (it already did nothing) * Character set detection with libmeegotouch is removed, only enca or libicu are supported * Meego-specific flags are gone from .desktop files * Functional tests have lost their vestigal Scratchbox and Aegis support There are 5 ontologies referencing Maemo, 4 of which are largely unused. These have been kept around in case anyone is using them outside Tracker. https://bugzilla.gnome.org/show_bug.cgi?id=783555
* Release 1.13.01.13.0Carlos Garnacho2017-05-231-1/+1
|
* Release 1.12.01.12.0Carlos Garnacho2017-03-201-2/+2
|
* Release 1.11.41.11.4Carlos Garnacho2017-02-281-1/+1
|
* configure.ac: Remove obsolete bits for 'external' media handlerSam Thursfield2017-02-061-13/+13
| | | | | There's no code to actually implement this nowadays, the configure.ac stuff is a relic.
* utils: Drop libgee dependencyCarlos Garnacho2017-01-241-3/+1
| | | | | It's only used on the tracker-resdump helper, and can be easily replaced with the GLib counterparts.
* Release 1.11.31.11.3Carlos Garnacho2017-01-181-1/+1
|
* configure: Make libseccomp only mandatory on linuxCarlos Garnacho2016-12-221-2/+9
| | | | | | | | If other unices want a similar level of protection, additional implementations should be added. In the mean time, it's just harsh to make tracker impossible to compile there. https://bugzilla.gnome.org/show_bug.cgi?id=764786
* configure: Disable libmediaart dependencyCarlos Garnacho2016-12-171-3/+3
| | | | | | | | | | Hopefully just temporarily. At the very least the processing should be taken out of the extractor threads, as it requires file operations that are not allowed there. In the worst case, we must reconsider this dependency, as it might become a window of opportunity to writing on the filesystem, even if on a very specific folder.
* Release 1.11.21.11.2Carlos Garnacho2016-12-081-1/+1
|
* configure: Make seccomp support mandatoryCarlos Garnacho2016-12-081-0/+2
| | | | | This is something we can do on master, older stable releases will have to stick to optional support.
* libtracker-common: Implement sandboxing through libseccompCarlos Garnacho2016-12-081-0/+20
| | | | | | | | | | The threads calling the new tracker_seccomp_init() function, and all threads/processes spawned from these, will enter a restricted mode where only a few sensible syscalls are allowed, and more specifically, filesystem/socket access are restricted to being respectively readonly and local only. https://bugzilla.gnome.org/show_bug.cgi?id=764786
* Release 1.11.11.11.1Carlos Garnacho2016-11-211-2/+2
| | | | The brown paper bag release that 1.11.0.1 was meant to be, because FML.
* Release 1.11.0.11.11.0.1bCarlos Garnacho2016-11-211-1/+1
| | | | For real, modify configure.ac
* libtracker-remote: Add support for application/sparql-results+xmlCarlos Garnacho2016-11-201-0/+1
| | | | | | | | As specified in https://www.w3.org/TR/rdf-sparql-XMLres/. This cursor implementation is able to read the XML expected under that content type. https://bugzilla.gnome.org/show_bug.cgi?id=773031
* Add libtracker-remoteCarlos Garnacho2016-11-201-0/+10
| | | | | | | | | | | | | | | This is yet another libtracker-sparql backend to connect to remote HTTP SPARQL endpoints. Connections are made explicitly through the tracker_sparql_connection_remote_new() API call, passing a server to connect to. This commit introduces support for application/sparql-results+json as specified in https://www.w3.org/TR/sparql11-results-json/. XML format will be handled next. Just readonly queries are supported, and provided there's no authentication schemes. https://bugzilla.gnome.org/show_bug.cgi?id=773031
* configure.ac: Bump version to 1.11.0Carlos Garnacho2016-10-191-1/+1
| | | | | Not much worth releasing yet, but having tracker-1.10 have a higher soname than master is confusing.
* Release 1.10.01.10.0Carlos Garnacho2016-09-191-2/+2
|
View Lorry Controller Status