<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fscrypt.git/tools.go, branch v0.2.7</title>
<subtitle>Go tool for managing Linux filesystem encryption
</subtitle>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/'/>
<entry>
<title>Manage tool versioning with Go modules (#161)</title>
<updated>2019-10-26T00:26:49+00:00</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey@google.com</email>
</author>
<published>2019-10-26T00:26:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=a3434e41bd482fc1b35703f66c24c9d1ec3b0be2'/>
<id>a3434e41bd482fc1b35703f66c24c9d1ec3b0be2</id>
<content type='text'>
See: https://github.com/golang/go/wiki/Modules#how-can-i-track-tool-dependencies-for-a-module

The tool code is never actually built, but the versions are still lock
in `go.mod` and `go.sum`. We can also simplify the Makefile.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
See: https://github.com/golang/go/wiki/Modules#how-can-i-track-tool-dependencies-for-a-module

The tool code is never actually built, but the versions are still lock
in `go.mod` and `go.sum`. We can also simplify the Makefile.</pre>
</div>
</content>
</entry>
</feed>
