pkgsrc

kpriv/pkgsrc

Fork 0

Commit graph

Author	SHA1	Message	Date
abs	847a0f9860	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 14:52:34 +00:00
agc	203292f73e	Add SHA512 digests for distfiles for net category Problems found with existing digests: Package haproxy distfile haproxy-1.5.14.tar.gz 159f5beb8fdc6b8059ae51b53dc935d91c0fb51f [recorded] da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated] Problems found locating distfiles: Package bsddip: missing distfile bsddip-1.02.tar.Z Package citrix_ica: missing distfile citrix_ica-10.6.115659/en.linuxx86.tar.gz Package djbdns: missing distfile djbdns-1.05-test25.diff.bz2 Package djbdns: missing distfile djbdns-cachestats.patch Package djbdns: missing distfile 0002-dnscache-cache-soa-records.patch Package gated: missing distfile gated-3-5-11.tar.gz Package owncloudclient: missing distfile owncloudclient-2.0.2.tar.xz Package poink: missing distfile poink-1.6.tar.gz Package ra-rtsp-proxy: missing distfile rtspd-src-1.0.0.0.tar.gz Package ucspi-ssl: missing distfile ucspi-ssl-0.70-ucspitls-0.1.patch Package waste: missing distfile waste-source.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.	2015-11-04 00:34:51 +00:00
abs	1c9a24edfd	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 16:15:37 +00:00

Author

SHA1

Message

Date

abs

847a0f9860

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 14:52:34 +00:00

agc

203292f73e

Add SHA512 digests for distfiles for net category

Problems found with existing digests:
	Package haproxy distfile haproxy-1.5.14.tar.gz
	159f5beb8fdc6b8059ae51b53dc935d91c0fb51f [recorded]
	da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated]

Problems found locating distfiles:
	Package bsddip: missing distfile bsddip-1.02.tar.Z
	Package citrix_ica: missing distfile citrix_ica-10.6.115659/en.linuxx86.tar.gz
	Package djbdns: missing distfile djbdns-1.05-test25.diff.bz2
	Package djbdns: missing distfile djbdns-cachestats.patch
	Package djbdns: missing distfile 0002-dnscache-cache-soa-records.patch
	Package gated: missing distfile gated-3-5-11.tar.gz
	Package owncloudclient: missing distfile owncloudclient-2.0.2.tar.xz
	Package poink: missing distfile poink-1.6.tar.gz
	Package ra-rtsp-proxy: missing distfile rtspd-src-1.0.0.0.tar.gz
	Package ucspi-ssl: missing distfile ucspi-ssl-0.70-ucspitls-0.1.patch
	Package waste: missing distfile waste-source.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

2015-11-04 00:34:51 +00:00

abs

1c9a24edfd

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 16:15:37 +00:00

3 commits