diff options
| author | lhchavez <[email protected]> | 2021-10-14 04:42:42 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-10-14 04:42:42 -0700 |
| commit | 6eae74c128e37e590d3a5da3fe0561add4b94d5c (patch) | |
| tree | bd5d11a80188bc44668cce5deed56c949151da01 /README.md | |
| parent | 9b155184fe1f0f0258730bccd2759ac7ec39be2a (diff) | |
libgit2 v1.3.0 #major (#840)
This commit introduces libgit2 v1.3.0 to git2go, which brings a large
number of [bugfixes and
features](https://github.com/libgit2/libgit2/releases/tag/v1.3.0).
This also marks the start of the v33 release.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 13 |
1 files changed, 7 insertions, 6 deletions
@@ -10,7 +10,8 @@ Due to the fact that Go 1.11 module versions have semantic meaning and don't nec | libgit2 | git2go | |---------|---------------| -| main | (will be v33) | +| main | (will be v34) | +| 1.3 | v33 | | 1.2 | v32 | | 1.1 | v31 | | 1.0 | v30 | @@ -18,13 +19,13 @@ Due to the fact that Go 1.11 module versions have semantic meaning and don't nec | 0.28 | v28 | | 0.27 | v27 | -You can import them in your project with the version's major number as a suffix. For example, if you have libgit2 v1.2 installed, you'd import git2go v32 with: +You can import them in your project with the version's major number as a suffix. For example, if you have libgit2 v1.2 installed, you'd import git2go v33 with: ```sh -go get github.com/libgit2/git2go/v32 +go get github.com/libgit2/git2go/v33 ``` ```go -import "github.com/libgit2/git2go/v32" +import "github.com/libgit2/git2go/v33" ``` which will ensure there are no sudden changes to the API. @@ -48,7 +49,7 @@ This project wraps the functionality provided by libgit2. If you're using a vers When linking dynamically against a released version of libgit2, install it via your system's package manager. CGo will take care of finding its pkg-config file and set up the linking. Import via Go modules, e.g. to work against libgit2 v1.2 ```go -import "github.com/libgit2/git2go/v32" +import "github.com/libgit2/git2go/v33" ``` ### Versioned branch, static linking @@ -78,7 +79,7 @@ In order to let Go pass the correct flags to `pkg-config`, `-tags static` needs One thing to take into account is that since Go expects the `pkg-config` file to be within the same directory where `make install-static` was called, so the `go.mod` file may need to have a [`replace` directive](https://github.com/golang/go/wiki/Modules#when-should-i-use-the-replace-directive) so that the correct setup is achieved. So if `git2go` is checked out at `$GOPATH/src/github.com/libgit2/git2go` and your project at `$GOPATH/src/github.com/my/project`, the `go.mod` file of `github.com/my/project` might need to have a line like - replace github.com/libgit2/git2go/v32 ../../libgit2/git2go + replace github.com/libgit2/git2go/v33 ../../libgit2/git2go Parallelism and network operations ---------------------------------- |