grive-sync: Remove "$HOME" subdirectory requirement

[KreAch3R]

Check #383

[vitalif]

Hi. Just remove it, don't comment it out
This script was contributed by someone here in PRs so I have no idea why it was limited to $HOME

[KreAch3R]

Hi. Just remove it, don't comment it out This script was contributed by someone here in PRs so I have no idea why it was limited to $HOME

Hello, ah, ok. Done. If you are interested in clean code, I can try to force push another clean commit but I'm not sure how the PR is going to handle it.

[jankatins]

The test is alright (assuming -z tests for "not defined"), but the msg should be "need a directory as either absolute path or relative to $HOME"

[KreAch3R]

You were right. I took a better look and what exactly was happening and it was all about a "/"....

[jankatins]

Right now I feel that the original test is better suited: if I would configure the script to sync opt/whatever, I would be very suprised if it would use /opt/whatever and not ${HOME}/opt/whatever (for the former, i would want to configure /opt/whatever with a leading slash). For that reason, I would go with just changing the help message:

if [[ -z "${DIRECTORY}" ]] || [[ ! -d "${DIRECTORY}" ]] ; then
	echo "Need a directory name (absolute or relative to the current users home directory) as second argument. Got ${DIRECTORY}. Aborting."
	exit 1
fi

I've actually adjusted that in my local version of the script which I started with systemctl --user start $(systemd-escape --template=grive@.service -- "${HOME}/.gdrive"), so an absolute path.

[jankatins]

See #389 for my version