Skip to content

Update README.md #1149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Secondarymaster wants to merge 1 commit into
base: v2-to-v3-migration
Choose a base branch
from
+3 −3
Open

Update README.md #1149

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,21 +82,21 @@ The above setup will ensure that the drive binary after compilation can be invok
To install from the latest source, run:

```shell
$ go get -u github.com/odeke-em/drive/cmd/drive
$ go install github.com/odeke-em/drive/cmd/drive@latest
```

Otherwise:

* In order to address [issue #138](https://github.com/odeke-em/drive/issues/138), where debug information should be bundled with the binary, you'll need to run:

```shell
$ go get github.com/odeke-em/drive/drive-gen && drive-gen
$ go install github.com/odeke-em/drive/drive-gen@latest && drive-gen
```

In case you need a specific binary e.g for Debian folks [issue #271](https://github.com/odeke-em/drive/issues/271) and [issue 277](https://github.com/odeke-em/drive/issues/277)

```shell
$ go get -u github.com/odeke-em/drive/drive-google
$ go install github.com/odeke-em/drive/drive-google@latest
```

That should produce a binary `drive-google`
Expand Down