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

33 lines
1,004 B
Makefile
Raw Normal View History

Recursive revbump from boost update
2017-04-30 03:21:19 +02:00
# $NetBSD: Makefile,v 1.8 2017/04/30 01:21:56 ryoon 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
DISTNAME= grive2-0.4.1
Recursive revbump from boost update
2017-04-30 03:21:19 +02:00
PKGREVISION= 5
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
CATEGORIES= net
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
MASTER_SITES= ${MASTER_SITE_GITHUB:=vitalif/}
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
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= https://github.com/vitalif/Grive2
COMMENT= Independent open source implementation of Google Drive client
LICENSE= gnu-gpl-v2
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
GITHUB_TAG=v${PKGVERSION_NOREV}
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
USE_CMAKE= yes
Needs pkg-config.
2015-06-25 09:37:58 +02:00
USE_TOOLS+= pkg-config
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
USE_LANGUAGES= c c++
SUBST_CLASSES+= manpath
SUBST_MESSAGE.manpath= Fix manpath
SUBST_STAGE.manpath= pre-configure
SUBST_FILES.manpath= bgrive/CMakeLists.txt grive/CMakeLists.txt
SUBST_SED.manpath= -e 's,DESTINATION share/man,DESTINATION ${PKGMANDIR},g'
.include "../../security/libgcrypt/buildlink3.mk"
.include "../../textproc/expat/buildlink3.mk"
.include "../../devel/boost-libs/buildlink3.mk"
.include "../../devel/cppunit/buildlink3.mk"
.include "../../devel/yajl/buildlink3.mk"
.include "../../devel/zlib/buildlink3.mk"
.include "../../www/curl/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink