<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/go1.4.go, branch xattr_user_buffer</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2020-04-13T12:54:04+00:00</updated>
<entry>
<title>dep: migrate to Go Modules</title>
<updated>2020-04-13T12:54:04+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2020-04-13T11:59:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=cad711993d67dd920f9749a09414dbbba6ab8136'/>
<id>urn:sha1:cad711993d67dd920f9749a09414dbbba6ab8136</id>
<content type='text'>
Following https://blog.golang.org/migrating-to-go-modules
</content>
</entry>
<entry>
<title>Add "dep" files: Gopkg.toml and Gopkg.lock</title>
<updated>2017-09-06T18:52:30+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-09-06T18:52:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=512be8f081d2cc2afc778a2dcf5447647de2bbea'/>
<id>urn:sha1:512be8f081d2cc2afc778a2dcf5447647de2bbea</id>
<content type='text'>
Allows users to get a reproduceable build. Still needs to
be integrated into build.bash.

Suggested at https://github.com/rfjakob/gocryptfs/issues/142
</content>
</entry>
<entry>
<title>main: rework "you need Go 1.5" lockout to make "go vet" happy</title>
<updated>2017-08-15T10:52:40+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-08-15T10:48:02+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=affb1c2f6617d66bdc9fda41b017e0de000c3691'/>
<id>urn:sha1:affb1c2f6617d66bdc9fda41b017e0de000c3691</id>
<content type='text'>
When you run "go vet" explicitely against go1.4.go, it ignores
the "+build !go1.5" tag and, of course, throws a syntax error:

  $ go vet go1.4.go
  can't load package: package main:
  go1.4.go:5:1: expected 'package', found 'STRING' "You need Go 1.5 or higher to compile gocryptfs!"

Unfortunatey, this is how https://goreportcard.com/ seems to call
"go vet", and means we get 0% on the "go vet" test and see this
error:

  An error occurred while running this test (strconv.Atoi: parsing " go1.4.go": invalid syntax)

By reworking the logic to use a non-existant package we get an
uglier error

  $ GOROOT=/opt/go1.4.3 /opt/go1.4.3/bin/go build
  go1.4.go:7:8: cannot find package "You_need_Go_1.5_or_higher_to_compile_gocryptfs" in any of:
  	/opt/go1.4.3/src/You_need_Go_1.5_or_higher_to_compile_gocryptfs (from $GOROOT)
  	/home/jakob/go/src/You_need_Go_1.5_or_higher_to_compile_gocryptfs (from $GOPATH)
  profiling.go:6:2: cannot find package "runtime/trace" in any of:
  	/opt/go1.4.3/src/runtime/trace (from $GOROOT)
  	/home/jakob/go/src/runtime/trace (from $GOPATH)

but make "go vet" happy.
</content>
</entry>
<entry>
<title>build.bash: implement "you need Go 1.5" lockout in pure Go</title>
<updated>2017-08-02T21:41:20+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-08-02T21:34:14+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=e4fdb424964599db2e8d0ab273b6be804c6c9c12'/>
<id>urn:sha1:e4fdb424964599db2e8d0ab273b6be804c6c9c12</id>
<content type='text'>
As noticed by @riking, the logic in the bash script will break
when Go 1 version numbers reach double-digits.

Instead, use a build tag "!go1.5" to cause a syntax error:

  $ /opt/go1.4.3/bin/go build
  can't load package: package github.com/rfjakob/gocryptfs:
  go1.4.go:5:1: expected 'package', found 'STRING' "You need Go 1.5 or higher to compile gocryptfs!"

Fixes https://github.com/rfjakob/gocryptfs/issues/133
</content>
</entry>
</feed>
