Hi all,
So I spent some time last week working on this. I said in some earlier
conversations with the maintainers that I would like to take things back
to basics a bit using a more "git" like approach to tracker so it
becomes more powerful on the command line.
Branch?
---
As part of thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martyn,
I like this idea a lot. Would it also be possible to make
tracker-$name in argv[0] to be recognized by the new 'tracker'
command's command line parsing to be the same as $name in argv[1]?
Then for one release we could just make symlinks fr
On 06/10/14 13:12, Philip Van Hoof wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martyn,
HI,
I like this idea a lot. Would it also be possible to make
tracker-$name in argv[0] to be recognized by the new 'tracker'
command's command line parsing to be the same as $name in argv[1]?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/10/2014 15:21, Martyn Russell wrote:
Hi,
> In principal it's possible, but the question is more about "where"
> this is done. This is probably more of a packaging job than
> anything (other than 'tracker' itself handling it (which is trivial
> t
This is all too excellent!
Is there also "tracker search" and "tracker stats"?
Also, after all this, I suppose there would only be 2 other
executables... tracker-preferences and tracker-needle?
___
tracker-list mailing list
tracker-list@gnome.org
https:
On 06/10/14 20:14, Tshepang Lekhonkhobe wrote:
This is all too excellent!
Is there also "tracker search" and "tracker stats"?
Now tracker-stats is part of tracker-status:
$ tracker status
$ tracker status --stat [-a] [[expression1]...]
$ tracker status --collect-debug-info
Running on i
On 06/10/14 14:51, Philip Van Hoof wrote:
if (strcmp($name, "control") == 0) {
if (argv[2] in options for index) {
use index for argv[1]
}
if (argv[2] in options for daemon) {
use daemon for argv[1]
}
if (argv[2] in --hard, -