On 2015/11/13 23:12, Rafael Sadowski wrote:
> Hey @ports,
> 
> I asked sthen@ to remove sysutils/grive from ports tree last week. The
> old grive is dead and not support the new google drive REST API.
> 
> I've found a fork which is current under development. Tested on amd64
> with my private google drive account.
> 
> If you will test without the tarball checkout openbsd-wip:
> 
> https://github.com/jasperla/openbsd-wip/tree/master/sysutils/grive2
> 
> DESCR:
> 
> grive2 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.
> 
> 
> Comments? OK?
> 
> Best regards,
> 
> Rafael

With the license marker changed to "GPLv2 only" it's OK with me to
import.

It could do with a quirks change too.

Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/quirks/Makefile,v
retrieving revision 1.313
diff -u -p -r1.313 Makefile
--- Makefile    13 Nov 2015 12:55:36 -0000      1.313
+++ Makefile    14 Nov 2015 13:14:02 -0000
@@ -5,7 +5,7 @@ CATEGORIES =    devel databases
 DISTFILES =
 
 # API.rev
-PKGNAME =      quirks-2.158
+PKGNAME =      quirks-2.159
 PKG_ARCH =     *
 MAINTAINER =   Marc Espie <es...@openbsd.org>
 
Index: files/Quirks.pm
===================================================================
RCS file: /cvs/ports/devel/quirks/files/Quirks.pm,v
retrieving revision 1.323
diff -u -p -r1.323 Quirks.pm
--- files/Quirks.pm     13 Nov 2015 12:55:36 -0000      1.323
+++ files/Quirks.pm     14 Nov 2015 13:14:02 -0000
@@ -386,6 +386,7 @@ my $stem_extensions = {
        'icinga2-pgsql' => 'icinga2-ido-pgsql',
        'rcsparse' => 'py-rcsparse',
        'tesseract-dan-frak' => 'tesseract-dan_frak',
+       'grive' => 'grive2',
 };
 
 # reasons for obsolete packages
@@ -688,7 +689,6 @@ my $obsolete_reason = {
        'node-syslog' => 7,
        'gtk2hs-buildtools' => 5,
        'coffeescript' => 7,
-       'grive' => 3,
        'pb-browser' => 0,
        'unace' => 0,
 };

Reply via email to