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

Explain region hold.

Snapshot Isolation Level

Three Issues With Using Database Generated IDs

Example of table with auto-increment id.

Sorting Algorithms

The fifteen minute WebRTC demo

The method of exploration

How to Set up Multiple Monitors on Windows 10

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 Booking.com. I write about tech, mostly *nix, JS & Go. Also life stuff, learning languages and hobbies. https://threkk.com

More from Medium

Evolution of Distributed Systems

Go bits: Magic with functions

When IO-bound Hides Inside CPU

Goroutine leaks and how to handle them