summaryrefslogtreecommitdiff
path: root/go1.4.go
diff options
context:
space:
mode:
authorJakob Unterwurzacher2017-08-02 23:34:14 +0200
committerJakob Unterwurzacher2017-08-02 23:41:20 +0200
commite4fdb424964599db2e8d0ab273b6be804c6c9c12 (patch)
tree358e489ce40a86cfe5963d6f303d859396947d11 /go1.4.go
parent1f39ede4b46ec3609ccbe1d54402f4a17f3d697e (diff)
build.bash: implement "you need Go 1.5" lockout in pure Go
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
Diffstat (limited to 'go1.4.go')
-rw-r--r--go1.4.go5
1 files changed, 5 insertions, 0 deletions
diff --git a/go1.4.go b/go1.4.go
new file mode 100644
index 0000000..939fe91
--- /dev/null
+++ b/go1.4.go
@@ -0,0 +1,5 @@
+// +build !go1.5
+
+// Cause an early compile error on Go 1.4 an lower. We need Go 1.5 for a number
+// of reasons, among them NewGCMWithNonceSize and RawURLEncoding.
+"You need Go 1.5 or higher to compile gocryptfs!"