Can't sync directory outside home

[KreAch3R]

Hello,

Is there a vital reason that the google-drive folder needs to be a subdirectory to $HOME? My google-drive location is /media/Data/GoogleDrive (this is a /media mounted second HDD in NTFS) and I am getting these errors in the service runs:

Need a directory name in the current users home directory as second argument. Aborting

If I run grive inside the correct folder manually though, it runs. Can I remove the relevant if statement

grive2/systemd/grive-sync.sh

Lines 20 to 23 in 648ff8e

	if [[ -z "$DIRECTORY" ]] || [[ ! -d "$DIRECTORY" ]] ; then
	echo "Need a directory name in the current users home directory as second argument. Aborting."
	exit 1
	fi

or will it break everything?

[jankatins]

You probably already can simply start it with a absolute path and it will work. I think... This was there because the default uses HOME for relative path and when I wrote that I was only thinking about relative paths.

[KreAch3R]

Ok, so I can probably check if I can remove it and if it breaks, given that you didn't think of something completely important that needs the path to be inside $HOME. I was thinking you did it because of permissions.

[KreAch3R]

I just commented out the lines and syncing with the service files seem to work. I created a PR, I commented them out, I was not sure you would want to have them completely removed in case something breaks and you weren't sure it would work.

[KreAch3R]

Check https://github.com/vitalif/grive2/compare/ed548946e443539de5d09076e793fbb15229a483..a9775e5229928b554c1863362b2162e35d318197,
the real problem was all about a slash.

[jankatins]

See #389 for a PR changing the error message (the code already works like that)