| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Make these explicit to make future design discussions easier.
Goals can of course be changed in future as the project evolves.
|
| |
|
| |
|
|
|
|
| |
See https://gitlab.gnome.org/infrastructure/infrastructure/issues/212
|
|
|
|
|
| |
Confusing bugs can occur if you use the CLI from /usr with
in-development versions of the daemons.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes https://gitlab.gnome.org/GNOME/tracker/issues/111 and also
simplifies the instructions in the README for running Tracker from
the build tree.
The sandbox utility is now executed from the top directory by running:
python3 -m utils.trackertestutils
Previously, due to importing stuff from trackertestutils. you needed to
run it from the utils/ directory or set PYTHONPATH appropriately.
Additionally, tracker-miners.git will ship a 'run-uninstalled' script
to provide convenient access to the sandbox script and allow running
Tracker from the build tree.
|
|
|
|
|
|
|
|
| |
This talks about how to enable different kinds of logging output from
the functional tests, now that the previous commit has introduced some
sanity into the logging.
Attaching debugger is also discussed.
|
|
|
|
|
|
|
|
|
|
|
| |
The `tracker-sandbox` tool is now a thin wrapper around the `tracker`
CLI. Effectively, this commit removes all functionality except the old
'--shell' mode. This way we avoid duplicating code paths and we make
sure that everyone is using and testing the `tracker` CLI.
The sandbox tool now captures all log output from the Tracker daemons,
instead of having them print directly to stdout. The old behaviour is
now enabled with the `--verbosity=` argument.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The README instructions are aimed at developers who want to develop and
test Tracker. We now point to the "official" workflow for developing
GNOME core components, and we document our own tooling. We no longer
recommend that users install anything into /usr because only
distributions should be doing that.
Fixes https://gitlab.gnome.org/GNOME/tracker/issues/105
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the tools referenced in "Running Tracker" don't exist any more.
We shouldn't need to document how to set inotify limits as distros
should be setting inotify limits high enough for Tracker to work out of
the box.
The man pages referred in the "Further help" section are nice, but
ideally they'd be linked from the main documentation at
https://wiki.gnome.org/Projects/Tracker (see
https://gitlab.gnome.org/GNOME/tracker/issues/107).
|
|
|
|
|
|
| |
Let's do our best to avoid confusion.
Also link to gnome-online-miners.
|
|
|
|
|
| |
This information is duplicated in the project wiki, which we already
link to.
|
|
|
|
|
|
| |
The Roadmap link is removed as it's not up to date. The Issue Tracker link
is removed because it's part of the gitlab.gnome.org project. The other
links are reordered with website first and communication channels last.
|
|
|