Skip to content
This repository
Browse code

preparing for v0.1.0 release

  • Loading branch information...
commit b6fb4a604e51009ece1d8cfe7b45ed603097b47c 1 parent da6c990
Matchman Green match065 authored

Showing 2 changed files with 19 additions and 8 deletions. Show diff stats Hide diff stats

  1. +1 1  CMakeLists.txt
  2. +18 7 README
2  CMakeLists.txt
... ... @@ -1,6 +1,6 @@
1 1 cmake_minimum_required(VERSION 2.8)
2 2
3   -set( GRIVE_VERSION "0.1.0-pre" )
  3 +set( GRIVE_VERSION "0.1.0" )
4 4
5 5 add_subdirectory( libgrive )
6 6 add_subdirectory( grive )
25 README
@@ -2,18 +2,28 @@ Grive 0.1.0
2 2
3 3 Grive is still considered experimental. It just downloads all the files in your google drive
4 4 into the current directory. After you make some changes to the local files, run grive and
5   -it will upload your changes back to your google drive.
  5 +it will upload your changes back to your google drive. New files created in local or google
  6 +drive will be uploaded or downloaded respectively. Deleted files will also be "removed".
  7 +Currently Grive will NOT destroy any of your files: it will only rename local files to
  8 +start with a dot, or put it in the google drive trash. You can always recover them.
6 9
7 10 There are a few things that grive does not do at the moment:
8 11 - wait for changes in file system to occur and upload. Grive only sync when you run it.
9   -- create new files in google drive. Grive only uploads changed files that already
10   - exist in server.
11 12
12 13 Of course these will be done in future, possibly the next release.
13 14
14 15 This is compiled in Fedora 16 x64. You need the following libraries to run:
15   -json-c, libcurl, libstdc++ and openssl. CppUnit is also optional and required
16   -only if you want to build the test cases.
  16 +
  17 +- json-c
  18 +- libcurl
  19 +- libstdc++
  20 +- openssl
  21 +- Boost (Boost filesystem is required)
  22 +
  23 +There are also some optional dependencies:
  24 +- CppUnit (for unit tests)
  25 +- libbfd (for backtrace)
  26 +- binutils
17 27
18 28 When grive is ran for the first time, you should use the "-a" argument to grant
19 29 permission to grive to access to your Google Drive. An URL should be printed.
@@ -21,7 +31,8 @@ Go to the link. You will need to login to your google account if you haven't
21 31 done so. After granting the permission to grive, the browser will show you
22 32 an authenication code. Copy-and-paste that to the standard input of grive.
23 33
24   -If everything works fine, grive will create a .grive file in your home directory.
25   -It will also start downloading files from your Google Drive to your current directory.
  34 +If everything works fine, grive will create a .grive and a .grive_state file in your
  35 +current directory. It will also start downloading files from your Google Drive to
  36 +your current directory.
26 37
27 38 Enjoy!

0 comments on commit b6fb4a6

Please sign in to comment.
Something went wrong with that request. Please try again.