grive upload itself to Google Drive

[OpenNingia]

I created a folder "My Google Drive" in my home directory then copied "grive" executable inside.
Then I launched ./grive and it updates my files as it should.

However at the end of the sync process it uploaded itself to the google drive. I believe this is not intended ( as grive already ignores the .grive and .grive_state files it should also ignore the executable )

[sgbeal]

FWIW, i disagree that the name "grive" (without a dot) should be considered magical. It is a legitimate (though unusual) file/folder name for arbitrary users. Having the grive binary IN the directory to be synching is kind of like installing the dropbox binaries under ~/Dropbox oder the Ubuntu One binaries under ~/Ubuntu One (i still can't BELIEVE they put a space in the dir name!). IMHO that's just "bad practice."

[OpenNingia]

@sgbeal at the moment gdrive synchronize the files in the launching directory, so this is what we get.
However I never suggested to filter the "gdrive" file but the executable file name. Every program receive its own name as starting parameter ( argv[0] for tech users ) so it should be legitimate to filter itself, whatever the file name is.

[sgbeal]

Filtering out argv[0] sounds like a very graceful solution :).

[match065]

Agreed that argv[0] is a very graceful solution. Once we implement the ignore list feature, we can put argv[0] there.

[estomagado]

I respectfully disagree. If you willingly put the grive executable inside the sync path, it's because you want it to be synchronized.

If you don't want grive to be sync'd, why not put it on your exec path? (Which is, as I understand, standard procedure.)

Mine is at /home/username/bin, and you can always put it on /usr/local/bin if you have root privileges and want Grive to be available to all users.

Anyway, if this proves to be a popular request (even if I don't like it, get outvoted is one aspect of democracy) we maybe can think of a switch to filter (or not to filter) the grive executable.