kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/net/grive2/distinfo

9 lines
559 B
Text
Raw Normal View History

Updated net/grive2 to 0.4.1 Changelog only has "Bug fixes" Several pkgsrc patches merged pkgsrc changes: Switch to new Github handling
2015-11-09 15:52:34 +01:00
$NetBSD: distinfo,v 1.3 2015/11/09 14:52:34 abs Exp $
Added net/grive2 version 0.4.0.20150531 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 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.
2015-06-16 18:15:37 +02:00
Updated net/grive2 to 0.4.1 Changelog only has "Bug fixes" Several pkgsrc patches merged pkgsrc changes: Switch to new Github handling
2015-11-09 15:52:34 +01:00
SHA1 (grive2-0.4.1.tar.gz) = f20da164b63f0acb1d15620d44f5596feed3344b
RMD160 (grive2-0.4.1.tar.gz) = 46ecbfa294e5e804c8837e3ba2667a13a54a57a8
SHA512 (grive2-0.4.1.tar.gz) = 55523f09afaad3e249fad6a085bcbb19d785f200bbe4ef45d48e6f6a44a41d13f0b8e77de348def819bf5409f1a995147fbb058191cda991aef023c76f2dbcf0
Size (grive2-0.4.1.tar.gz) = 158861 bytes
Added net/grive2 version 0.4.0.20150531 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 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.
2015-06-16 18:15:37 +02:00
SHA1 (patch-libgrive_CMakeLists.txt) = fa81eae7f6c70478c757c897fab3fb1d297b25b0
SHA1 (patch-libgrive_src_util_OS.cc) = ac5a59b717af6029134eb299b36a5862df193c38
Reference in a new issue Copy permalink