Package Details: drive

Git Clone URL: (read-only)
Package Base: drive
Description: Pull or push Google Drive files
Upstream URL:
Licenses: Apache
Conflicts: drive-git
Submitter: shaggytwodope
Maintainer: shaggytwodope
Last Packager: shaggytwodope
Votes: 56
Popularity: 0.408113
First Submitted: 2015-01-03 01:12
Last Updated: 2017-02-03 19:13

Latest Comments

schulz commented on 2017-11-19 00:19

I got the same bug as @dlh, when using pacaur, it didn't find the bin subdirectory for some reason. I cleared the pacaur cache and tried again and it worked just fine. I am not sure what was the cause, probably something that only shows up sporadically.

Anyway, thanks for the excellent work!

shaggytwodope commented on 2017-07-01 16:23

@martyg Not sure this is build related at all. You've opened an issue on github. I think now it's best wait til odeke can get back to you. Debugging this falls to him.

martyg commented on 2017-06-29 00:14

I am having trouble getting drive push to work on binary files once modified.

Any chance this is a build, as opposed to upstream, issue?

When I built this package, makepkg left behind zero-size prepare.log and package.log files. I assume this indicates a clean build?

shaggytwodope commented on 2016-10-17 07:18

@lonaowna Appreciated mate. It's been updated accordingly.

lonaowna commented on 2016-10-17 07:09

The .install file it not needed. The same function is already handled by /usr/share/libalpm/hooks/gtk-update-icon-cache.hook

minami commented on 2016-10-15 12:01

@shaggytwodope Sorry for the late response, I must have disabled notifications. I don't find "drive help" enough because it doesn't say anything about configuration, directory initialization, what is drive-server, why do I need it and how to configure it. It's just in the readme.

shaggytwodope commented on 2016-06-25 12:50

@minami Indeed, I'll try to talk to the dev about a man page. If not include the readme somehow and mention it in a post install msg maybe. Is the output of "drive help" not useful enough?

minami commented on 2016-06-25 10:56

First of all, thank you for the package! I have just a small RFE. Since the command lacks a man page, could the package at least bundle repository's

shaggytwodope commented on 2016-05-29 23:25

@lesto, What do you mean by official package system?, we need some libs to build.

There is some talk exploring depth=1 type stuff with go. But it's not released yet. Expect this to solve it's self in 1.7 release. It is not git you are using, rather like go + git.

When I get time later today I'll explore speeding things up or maybe even showing progress better if that is an issue for anyone. But reasonably it shouldn't hang that badly. Unless you're net and cpu is a bit on the slow side.. then I can't help that currently. If you can think of anything to fix or speed it up let me know and I'll do it asap.

Thanks for feedback ~ John

lesto commented on 2016-05-29 15:14

why you use "go get git" instead of official package system? could at least set depth=1 and only needed branch, maybe even a bit of feedback? that prepare() method is taking a long time and seems freezed.

All comments