installing grive on macOS through homebrew

.dockerignore

@@ -0,0 +1,5 @@
+*
+!cmake
+!grive
+!libgrive
+!CMakeLists.txt

.gitignore

@@ -14,3 +14,14 @@ bgrive/bgrive
 grive/grive
 libgrive/btest
 *.cmake
+
+debian/debhelper-build-stamp
+debian/files
+debian/grive.debhelper.log
+debian/grive.substvars
+debian/grive/
+debian/.debhelper
+
+obj-x86_64-linux-gnu/
+
+.idea

CMakeLists.txt

@@ -1,11 +1,27 @@
 cmake_minimum_required(VERSION 2.8)
+project(grive2)
+
+include(GNUInstallDirs)
 
 # Grive version. remember to update it for every new release!
-set( GRIVE_VERSION "0.5.1-dev" )
+set( GRIVE_VERSION "0.5.3" CACHE STRING "Grive version" )
+message(WARNING "Version to build: ${GRIVE_VERSION}")
 
 # common compile options
 add_definitions( -DVERSION="${GRIVE_VERSION}" )
 add_definitions( -D_FILE_OFFSET_BITS=64 -std=c++0x )
+if ( APPLE )
+	add_definitions( -Doff64_t=off_t )
+endif ( APPLE )
+
+find_program(
+	HAVE_SYSTEMD systemd
+	PATHS /lib/systemd /usr/lib/systemd
+	NO_DEFAULT_PATH
+)
+if ( HAVE_SYSTEMD )
+	add_subdirectory( systemd )
+endif( HAVE_SYSTEMD )
 
 add_subdirectory( libgrive )
 add_subdirectory( grive )

Dockerfile

@@ -0,0 +1,25 @@
+FROM alpine:3.7 as build
+
+RUN apk add make cmake g++ libgcrypt-dev yajl-dev yajl \
+	boost-dev curl-dev expat-dev cppunit-dev binutils-dev \
+	pkgconfig
+
+ADD . /grive2
+
+RUN mkdir /grive2/build \
+	&& cd /grive2/build \
+	&& cmake .. \
+	&& make -j4 install
+
+FROM alpine:3.7
+
+RUN apk add yajl libcurl libgcrypt boost-program_options boost-regex libstdc++ boost-system \
+	&& apk add boost-filesystem --repository=http://dl-cdn.alpinelinux.org/alpine/edge/main
+
+COPY --from=build /usr/local/bin/grive /bin/grive
+RUN chmod 777 /bin/grive \
+	&& mkdir /data
+
+VOLUME /data
+WORKDIR /data
+ENTRYPOINT grive

README.md

@@ -1,38 +1,144 @@
-# Grive2 0.5.1-dev
+# Grive2 0.5.3
 
-28 Sep 2016, Vitaliy Filippov
+09 Nov 2022, Vitaliy Filippov
 
 http://yourcmc.ru/wiki/Grive2
 
 This is the fork of original "Grive" (https://github.com/Grive/grive) Google Drive client
 with the support for the new Drive REST API and partial sync.
 
-Grive can be considered still beta or pre-beta quality. It simply downloads all the files in your
-Google Drive into the current directory. After you make some changes to the local files, run
+Grive simply downloads all the files in your Google Drive into the current directory.
+After you make some changes to the local files, run
 grive again and it will upload your changes back to your Google Drive. New files created locally
 or in Google Drive will be uploaded or downloaded respectively. Deleted files will also be "removed".
 Currently Grive will NOT destroy any of your files: it will only move the files to a
 directory named .trash or put them in the Google Drive trash. You can always recover them.
 
 There are a few things that Grive does not do at the moment:
 - continously wait for changes in file system or in Google Drive to occur and upload.
-  A sync is only performed when you run Grive.
+  A sync is only performed when you run Grive (there are workarounds for almost
+  continuous sync. See below).
 - symbolic links support.
 - support for Google documents.
 
-These may be added in the future, possibly the next release.
+These may be added in the future.
+
+Enjoy!
+
+## Usage
 
 When Grive is run for the first time, you should use the "-a" argument to grant
-permission to Grive to access to your Google Drive. A URL should be printed.
-Go to the link. You will need to login to your Google account if you haven't
-done so. After granting the permission to Grive, the browser will show you
-an authenication code. Copy-and-paste that to the standard input of Grive.
+permission to Grive to access to your Google Drive:
+
+```bash
+cd $HOME
+mkdir google-drive
+cd google-drive
+grive -a
+```
+
+A URL should be printed. Go to the link. You will need to login to your Google
+account if you haven't done so. After granting the permission to Grive, the
+authorization code will be forwarded to the Grive application and you will be
+redirected to a localhost web page confirming the authorization.
 
-If everything works fine, Grive will create .grive and .grive_state files in your
+If everything works fine, Grive will create .grive and .grive\_state files in your
 current directory. It will also start downloading files from your Google Drive to
 your current directory.
 
-Enjoy!
+To resync the direcory, run `grive` in the folder.
+
+```bash
+cd $HOME/google-drive
+grive
+```
+
+### Exclude specific files and folders from sync: .griveignore
+
+Rules are similar to Git's .gitignore, but may differ slightly due to the different
+implementation.
+
+- lines that start with # are comments
+- leading and trailing spaces ignored unless escaped with \
+- non-empty lines without ! in front are treated as "exclude" patterns
+- non-empty lines with ! in front are treated as "include" patterns
+  and have a priority over all "exclude" ones
+- patterns are matched against the filenames relative to the grive root
+- a/**/b matches any number of subpaths between a and b, including 0
+- **/a matches `a` inside any directory
+- b/** matches everything inside `b`, but not b itself
+- \* matches any number of any characters except /
+- ? matches any character except /
+- .griveignore itself isn't ignored by default, but you can include it in itself to ignore
+
+
+### Scheduled syncs and syncs on file change events
+
+There are tools which you can use to enable both scheduled syncs and syncs
+when a file changes. Together these gives you an experience almost like the
+Google Drive clients on other platforms (it misses the almost instantious
+download of changed files in the google drive).
+
+Grive installs such a basic solution which uses inotify-tools together with
+systemd timer and services. You can enable it for a folder in your `$HOME`
+directory (in this case the `$HOME/google-drive`):
+
+First install the `inotify-tools` (seems to be named like that in all major distros): 
+test that it works by calling `inotifywait -h`.
+
+Prepare a Google Drive folder in your $HOME directory with `grive -a`.
+
+```bash
+# 'google-drive' is the name of your Google Drive folder in your $HOME directory
+systemctl --user enable grive@$(systemd-escape google-drive).service
+systemctl --user start grive@$(systemd-escape google-drive).service
+```
+
+You can enable and start this unit for multiple folders in your `$HOME`
+directory if you need to sync with multiple google accounts.
+
+You can also only enable the time based syncing or the changes based syncing
+by only directly enabling and starting the corresponding unit:
+`grive-changes@$(systemd-escape google-drive).service` or 
+`grive-timer@$(systemd-escape google-drive).timer`.
+
+### Shared files
+
+Files and folders which are shared with you don't automatically show up in
+your folder. They need to be added explicitly to your Google Drive: go to the
+Google Drive website, right click on the file or folder and chose 'Add to My
+Drive'.
+
+### Different OAuth2 client to workaround over quota and google approval issues
+
+Google recently started to restrict access for unapproved applications:
+https://developers.google.com/drive/api/v3/about-auth?hl=ru
+
+Grive2 is currently awaiting approval but it seems it will take forever.
+Also even if they approve it the default Client ID supplied with grive may
+exceed quota and grive will then fail to sync.
+
+You can supply your own OAuth2 client credentials to work around these problems
+by following these steps:
+
+1. Go to https://console.developers.google.com/apis/api/drive.googleapis.com
+2. Choose a project (you might need to create one first)
+3. Go to https://console.developers.google.com/apis/library/drive.googleapis.com and
+   "Enable" the Google Drive APIs
+4. Go to https://console.cloud.google.com/apis/credentials and click "Create credentials > Help me choose"
+5. In the "Find out what credentials you need" dialog, choose:
+   - Which API are you using: "Google Drive API"
+   - Where will you be calling the API from: "Other UI (...CLI...)"
+   - What data will you be accessing: "User Data"
+6. In the next steps create a client id (name doesn't matter) and
+   setup the consent screen (defaults are ok, no need for any URLs)
+7. The needed "Client ID" and "Client Secret" are either in the shown download
+   or can later found by clicking on the created credential on
+   https://console.developers.google.com/apis/credentials/
+8. When you change client ID/secret in an existing Grive folder you must first delete
+   the old `.grive` configuration file.
+9. Call `grive -a --id <client_id> --secret <client_secret>` and follow the steps
+   to authenticate the OAuth2 client to allow it to access your drive folder.
 
 ## Installation
 
@@ -57,8 +163,14 @@ There are also some optional dependencies:
 On a Debian/Ubuntu/Linux Mint machine just run the following command to install all
 these packages:
 
-    sudo apt-get install git cmake build-essential libgcrypt11-dev libyajl-dev \
-        libboost-all-dev libcurl4-openssl-dev libexpat1-dev libcppunit-dev binutils-dev
+    sudo apt-get install git cmake build-essential libgcrypt20-dev libyajl-dev \
+        libboost-all-dev libcurl4-openssl-dev libexpat1-dev libcppunit-dev binutils-dev \
+        debhelper zlib1g-dev dpkg-dev pkg-config
+
+Fedora:
+
+    sudo dnf install git cmake libgcrypt-devel gcc-c++ libstdc++ yajl-devel boost-devel libcurl-devel expat-devel binutils zlib
+
 
 FreeBSD:
 
@@ -69,7 +181,7 @@ FreeBSD:
 On a Debian/Ubuntu/Linux Mint you can use `dpkg-buildpackage` utility from `dpkg-dev` package
 to build grive. Just clone the repository, `cd` into it and run
 
-    dpkg-buildpackage -j4
+    dpkg-buildpackage -j4 --no-sign
 
 ### Manual build
 
@@ -81,17 +193,35 @@ Grive uses cmake to build. Basic install sequence is
     make -j4
     sudo make install
 
+Alternativly you can define your own client_id and client_secret during build
+
+    mkdir build
+    cd build
+    cmake .. "-DAPP_ID:STRING=<client_id>" "-DAPP_SECRET:STRING=<client_secret>"
+    make -j4
+    sudo make install
+
 ## Version History
 
-### Grive2 v0.5.1-dev
+### Grive2 v0.5.3
+
+- Implement Google OAuth loopback IP redirect flow
+- Various small fixes
 
+### Grive2 v0.5.1
+
+- Support for .griveignore
+- Automatic sync solution based on inotify-tools and systemd
 - no-remote-new and upload-only modes
-- ignore regexp does not persist anymore (note that Grive will still track it to not
+- Ignore regexp does not persist anymore (note that Grive will still track it to not
   accidentally delete remote files when changing ignore regexp)
-- added options to limit upload and download speed
-- faster upload of new and changed files. now Grive uploads files without first calculating
+- Added options to limit upload and download speed
+- Faster upload of new and changed files. Now Grive uploads files without first calculating
   md5 checksum when file is created locally or when its size changes.
-- added -P/--progress-bar option to print ASCII progress bar for each processed file (pull request by @svartkanin)
+- Added -P/--progress-bar option to print ASCII progress bar for each processed file (pull request by @svartkanin)
+- Added command-line options to specify your own client_id and client_secret
+- Now grive2 skips links, sockets, fifos and other unusual files
+- Various small build fixes
 
 ### Grive2 v0.5
 
@@ -137,3 +267,4 @@ New features:
 - #87: support for revisions
 - #86: ~~partial sync (contributed by justin at tierramedia.com)~~ that's not partial sync,
   that's only support for specifying local path on command line
+

cmake/Modules/FindBFD.cmake

@@ -1,12 +1,6 @@
-find_library( DL_LIBRARY 	NAMES dl	PATH ${CMAKE_PLATFORM_IMPLICIT_LINK_DIRECTORIES} )
 find_library( BFD_LIBRARY	NAMES bfd	PATH ${CMAKE_PLATFORM_IMPLICIT_LINK_DIRECTORIES} )
 
-if ( DL_LIBRARY AND BFD_LIBRARY )
+if ( BFD_LIBRARY )
 	set( BFD_FOUND TRUE )
-endif (DL_LIBRARY AND BFD_LIBRARY)
-
-if ( BFD_FOUND )
-
 	message( STATUS "Found libbfd: ${BFD_LIBRARY}")
-
-endif ( BFD_FOUND )
+endif ( BFD_LIBRARY )

cmake/Modules/FindLibGcrypt.cmake

@@ -27,6 +27,9 @@ IF(LIBGCRYPTCONFIG_EXECUTABLE)
 
   EXEC_PROGRAM(${LIBGCRYPTCONFIG_EXECUTABLE} ARGS --cflags RETURN_VALUE _return_VALUE OUTPUT_VARIABLE LIBGCRYPT_CFLAGS)
 
+  string(REPLACE "fgrep: warning: fgrep is obsolescent; using grep -F" "" LIBGCRYPT_LIBRARIES "${LIBGCRYPT_LIBRARIES}")
+  string(STRIP "${LIBGCRYPT_LIBRARIES}" LIBGCRYPT_LIBRARIES)
+
   IF(${LIBGCRYPT_CFLAGS} MATCHES "\n")
     SET(LIBGCRYPT_CFLAGS " ")
   ENDIF(${LIBGCRYPT_CFLAGS} MATCHES "\n")

completion.zsh

@@ -0,0 +1,63 @@
+#compdef grive
+# ------------------------------------------------------------------------------
+# Copyright (c) 2015 Github zsh-users - http://github.com/zsh-users
+# All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions are met:
+#     * Redistributions of source code must retain the above copyright
+#       notice, this list of conditions and the following disclaimer.
+#     * Redistributions in binary form must reproduce the above copyright
+#       notice, this list of conditions and the following disclaimer in the
+#       documentation and/or other materials provided with the distribution.
+#     * Neither the name of the zsh-users nor the
+#       names of its contributors may be used to endorse or promote products
+#       derived from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+# DISCLAIMED. IN NO EVENT SHALL ZSH-USERS BE LIABLE FOR ANY
+# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+# (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+# LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+# ------------------------------------------------------------------------------
+# Description
+# -----------
+#
+#  Completion script for Grive (https://github.com/vitalif/grive2)
+#
+# ------------------------------------------------------------------------------
+# Authors
+# -------
+#
+#  * Doron Behar <https://github.com/doronbehar>
+#
+# ------------------------------------------------------------------------------
+# -*- mode: zsh; sh-indentation: 2; indent-tabs-mode: nil; sh-basic-offset: 2; -*-
+# vim: ft=zsh sw=2 ts=2 et
+# ------------------------------------------------------------------------------
+
+local curcontext="$curcontext" state line ret=1
+typeset -A opt_args
+
+_arguments -C \
+	'(-h --help)'{-h,--help}'[Produce help message]' \
+	'(-v --version)'{-v,--version}'[Display Grive version]' \
+	'(-a --auth)'{-a,--auth}'[Request authorization token]' \
+	'(-p --path)'{-p,--path}'[Root directory to sync]' \
+	'(-s --dir)'{-s,--dir}'[Single subdirectory to sync (remembered for next runs)]' \
+	'(-V --verbose)'{-V,--verbose}'[Verbose mode. Enable more messages than normal.]' \
+	'(--log-http)--log-http[Log all HTTP responses in this file for debugging.]' \
+	'(--new-rev)--new-rev[Create,new revisions in server for updated files.]' \
+	'(-d --debug)'{-d,--debug}'[Enable debug level messages. Implies -v.]' \
+	'(-l --log)'{-l,--log}'[Set log output filename.]' \
+	'(-f --force)'{-f,--force}'[Force grive to always download a file from Google Drive instead of uploading it.]' \
+	'(--dry-run)--dry-run[Only,detect which files need to be uploaded/downloaded,without actually performing them.]' \
+	'(--ignore)--ignore[Perl,RegExp to ignore files (matched against relative paths, remembered for next runs) ]' \
+	'*: :_files' && ret=0
+
+return ret