summaryrefslogtreecommitdiff
path: root/_posts/2013-7-11-goplus.md
diff options
context:
space:
mode:
authorBrian Picciano <bgp2396@bellsouth.net>2013-10-16 20:29:35 -0400
committerBrian Picciano <bgp2396@bellsouth.net>2013-10-16 20:29:35 -0400
commit19eba1a5f25c1c27216fcef20ef16241a235e54f (patch)
treec85f2eeecd9e0745c9f3c222547d4554758708ac /_posts/2013-7-11-goplus.md
parent9c2570133c66cf743a991c21f985377debfd6795 (diff)
fixed posts, got rid of sample posts
Diffstat (limited to '_posts/2013-7-11-goplus.md')
-rw-r--r--_posts/2013-7-11-goplus.md78
1 files changed, 78 insertions, 0 deletions
diff --git a/_posts/2013-7-11-goplus.md b/_posts/2013-7-11-goplus.md
new file mode 100644
index 0000000..0b76add
--- /dev/null
+++ b/_posts/2013-7-11-goplus.md
@@ -0,0 +1,78 @@
+---
+layout: post
+title: Go+
+categories:
+- go
+---
+
+Compared to other languages go has some strange behavior regarding its project
+root settings. If you import a library called `somelib`, go will look for a
+`src/somelib` folder in all of the folders in the `$GOPATH` environment
+variable. This works nicely for globally installed packages, but it makes
+encapsulating a project with a specific version, or modified version, rather
+tedious. Whenever you go to work on this project you'll have to add its path to
+your `$GOPATH`, or add the path permanently, which could break other projects
+which may use a different version of `somelib`.
+
+My solution is in the form of a simple script I'm calling go+. go+ will search
+in currrent directory and all of its parents for a file called `GOPROJROOT`. If
+it finds that file in a directory, it prepends that directory's absolute path to
+your `$GOPATH` and stops the search. Regardless of whether or not `GOPROJROOT`
+was found go+ will passthrough all arguments to the actual go call. The
+modification to `$GOPATH` will only last the duration of the call.
+
+As an example, consider the following:
+```
+/tmp
+ /hello
+ GOPROJROOT
+ /src
+ /somelib/somelib.go
+ /hello.go
+```
+
+If `hello.go` depends on `somelib`, as long as you run go+ from `/tmp/hello` or
+one of its children your project will still compile
+
+Here is the source code for go+:
+
+```bash
+#!/bin/sh
+
+SEARCHING_FOR=GOPROJROOT
+ORIG_DIR=$(pwd)
+
+STOPSEARCH=0
+SEARCH_DIR=$ORIG_DIR
+while [ $STOPSEARCH = 0 ]; do
+
+ RES=$( find $SEARCH_DIR -maxdepth 1 -type f -name $SEARCHING_FOR | \
+ grep -P "$SEARCHING_FOR$" | \
+ head -n1 )
+
+ if [ "$RES" = "" ]; then
+ if [ "$SEARCH_DIR" = "/" ]; then
+ STOPSEARCH=1
+ fi
+ cd ..
+ SEARCH_DIR=$(pwd)
+ else
+ export GOPATH=$SEARCH_DIR:$GOPATH
+ STOPSEARCH=1
+ fi
+done
+
+cd "$ORIG_DIR"
+exec go $@
+```
+
+# UPDATE: Goat
+
+I'm leaving this post for posterity, but go+ has some serious flaws in it. For
+one, it doesn't allow for specifying the version of a dependency you want to
+use. To this end, I wrote [goat][0] which does all the things go+ does, plus
+real dependency management, PLUS it is built in a way that if you've been
+following go's best-practices for code organization you shouldn't have to change
+any of your existing code AT ALL. It's cool, check it out.
+
+[0]: http://github.com/mediocregopher/goat