Versioned Go and the future of package management

A gopher moving packages around
Picture by Ashley McNamara CC BY-NC-SA 4.0

Once upon a time

Go packaging and distribution has been always a problem. Since the earliest versions, Go packaging relies on a directory in the machine where all the code is placed. This directory, stored in a global variable named $GOPATH, it doesn’t only have your source code, but also all the dependencies it uses. Dependencies are added and pulled from control…




Learn more about software development from the best Blue Harvest software engineers

Recommended from Medium

Linux Remote CLI Flutter Mobile App using python — CGI Programming.

Real Use Case of Ansible Expert session:

Zyro Website Builder as a Frontend for Facial Recognition Project

Dunder Data Challenge #3 — Optimal Solution

How I became a self taught programmer: from clueless kid to self taught programmer

Firebase Functions playaround

Tips for hiring remote web developers

Two Compression Algorithms I Came Up With

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Alberto de Murga

Alberto de Murga

Software engineer at I write about tech, mostly *nix, JS & Go. Also life stuff, learning languages and hobbies.

More from Medium

Golang automatic code formatting : Code like a Pro

Debugging terraform using Jetbrains GoLand

gorilla/mux 101 (rk-boot): Error handling

Serving a Node.js API on Amazon Elastic Kubernetes Service and CloudFront