Skip to main content

Can GB be my friend?

Vendoring with golang's tools sucks.
  • golang does not support enough D/VCS systems
  • GOROOT is now computed
  • GOPATH was once expected to be a single path but then someone added multi-path with the first path being the global vendor folder
  • in order to update the 'go get' you need to include the -u flag
  • when you use 'go get' the code include whatever submodule info like .git, .svn, .hg etc
There, I said it and I backed it up.

There are a few choices for vendoring projects in go. godep, nut, and the latest gb. I do not know anything about nut, however, godep works with the standard go tools. All you have to do is update GOPATH. On the other hand gb is a complete departure. Going the gb route means that you need to break backward compatibility with the standard tools. Since I'm new to gb I just do not know if it's a worthy solution.

The problem is not really obvious until you have multiple projects. And with each project you have to change your GOPATH so that the local project vendor files are used and not some other project. And it's not appropriate to share some vendor files as a matter of course.

There are a number of possible solutions that are user-based:\
  • keep your projects in separate containers
  • use a "select project" type script to update the environment
  • use a batch script for all go commands
  • modify the path and replace the go tool with your own per project and construct the environment
  • Makefile
** some of these are the same only different tool

Make is clearly still the solution to the problem. The go tools cannot be all things to all people and that is clear here. Sadly I wish the go tools could do just a little more in this space. Not all of the golang authors dislike make and it's also a pretty good goal.

I'm not sure I want to dump the go tools. if gb fails to impress I could always construct the environment with my own tools. And then I'm right where I started only with someone elses idea of what the ideal project layout is.

UPDATE: one of the biggest issues with gb is that it does not work with the various vim or emacs packages. Things like goimports have no idea what to do when GOPATH is not set.

FAIL: I have a use-case where my application is a huge template of go code. The template contents and the main.go file is resolved from the command line. For example my .sh file fills the environment with SQL fragments which I call a catalog. The build process takes a named root variable and resolves the rest.  Then it inserts all the values into the template as text/template does and produces the new main.go. First of all... this is a preprocessor step and gb does not support that. Second, gb supports multiple main(s) with branched folders in the main (cmd-ish) folder with one main per leaf folder. Sadly, generate could not find the proper artifacts to build and in fact broke the path.  Face it. gb is the preprocessor/wrapper that the go toolchain intended to subvert and now it's being wrapped again except that (a) cannot unwrap the default tools (b) is not a hybrid (b) is not idiomatic and I cannot wrap it again as I would the standard go tools.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…