Commit Graph

6 Commits

Author SHA1 Message Date
Steffen Godskesen
69e02ec294 vendor: add mattn/go-isatty 2018-11-14 14:35:29 -08:00
Taylor Blau
d68e51474e go.mod: depend on git-lfs/gitobj@v1.0.0
Since we have started tagging git-lfs/gitobj to be semantically
versioned, let's depend on that tag instead of the latest SHA-1 from
HEAD.

v1.0.0 is identical to the existing hash (1e97572956c1), so there are no
changes in vendor/, other than the pinned book-keeping.
2018-10-11 10:08:07 -07:00
brian m. carlson
902e855f32 go.mod: update gitobj to the latest master
In a future commit, we'll use the latest gitobj's untyped Object
function and storage functionality.  Update the repository to the latest
master and vendor the dependencies.
2018-09-11 17:43:19 +00:00
Taylor Blau
d32ff9b429 go.mod: use latest github.com/olekukonko/ts
We use package github.com/olekukonko/ts to issue IOCTL's to gather the
terminal size of the calling terminal in order to determine the length
of lines we attempt to print.

Until now, we have used revision ecf753e7c962, which is over 4 years
old. Since then, github.com/olekukonko/ts has introduced support for
Solaris, which we previously could not build or run on because package
syscall on Solaris does not export an IOCTL constant.

Let's upgrade to the latest version, and bring in support for Solaris.
2018-09-03 09:27:17 -04:00
Taylor Blau
8f0c44cde1 go.mod: pin github.com/git-lfs/wildmatch to v1.0.0
In order to prefer semantically versioned tags of our dependent
repositories over Go's date & SHA-1 format, let's tag
github.com/git-lfs/wildmatch.git at v1.0.0 (on the latest master) and
vendor it as such here.

The only change between b31c34466d64 and v1.0.0 is:

  * 83d2acb (Merge pull request #9 from git-lfs/ttaylorr/go-1.11,
    2018-08-31)
  * 2f71dd1 (.travis.yml: build on Go 1.11, 2018-08-30)
  * 4bab7d7 (go.mod: initial commit, 2018-08-30)

Which is the introduction of the go.mod file (and related changes).
Thus, there are no code changes between the two, so this is a safe
change to make.
2018-08-31 12:44:13 -04:00
Taylor Blau
114e85c200 all: use Go Modules instead of Glide
Since we are now building on Go 1.11 (as of 074a2d4f (all: use Go 1.11
in CI, 2018-08-28)) and Go 1.11 supports Go Modules [1], let's stop
using Glide, and begin using Go Modules.

This involves a few things:

  * Teach the Makefile how to build go.sum files instead of glide.lock
    files.

  * Teach continuous integration services to build Git LFS in a
    non-$GOPATH environment, since (without setting GO111MODULE=on
    explicitly, which we choose not to do), this will break compiling
    Git LFS, because Go 1.11 will ignore modules present in a Go
    checkout beneath $GOPATH.

  * In order to do the above, let's also make sure that we are
    un-setting $GOCACHE in the environment, as this causes Go to work
    without modules support [2].

  * Because we're no longer building in a `$GOPATH`-based location,
    let's instruct the CircleCI base image to archive the new location,
    too.

  * Similarly, teach the RPM spec to build in a non-$GOPATH location.

  * By contrast, since we use dh_golang to build git-lfs binaries on
    Debian, let's wait until the upstream dh_golang package is released
    with support for Go 1.11 module support explicitly. Therefore, force
    GO111MODULE to be on so that we can build a copy of Git LFS whose
    checkout is within a $GOPATH.

Although the go.mod versions match the glide.yaml ones, the diff
attached is large because Go Modules do not vendor `_test.go` files,
whereas Glide does.

[1]: https://golang.org/doc/go1.11#modules
[2]: `GOCACHE=on` will be deprecated in Go 1.12, so this change makes
     sense for that reason, too.

Co-authored-by: brian m. carlson <bk2204@github.com>
2018-08-29 13:25:47 -04:00