I’m a big fan of debian. I’m also a big fan of golang. One of the sacrifices debian makes to be so stable is lagging behind a bit on software versions. Debian users generally understand this, and also understand that it’s a good idea not to mess with the system versions of software. Here I will demonstrate how I configure my system to use whichever version of go I wish without harming the overall system configuration.

I’m a big fan of debian. I’m also a big fan of golang. One of the sacrifices debian makes to be so stable is lagging behind a bit on software versions. Debian users generally understand this, and also understand that it’s a good idea not to mess with the system versions of software. Here I will demonstrate how I configure my system to use whichever version of go I wish without harming the overall system configuration.

  • Elw@lemmy.sdf.org
    3·
    3 months ago

    Good article. I learned long ago that, at least the case of your development environment, it’s best to install the latest upstream release instead of just relying on the system provided version. Go makes doing this extremely easy relative to some other languages out there.

    • h0bbl3s@lemmy.worldOP
      1·
      3 months ago

      Thanks :) Exactly. I do a lot of development and testing in an alpine linux container, simply because it has much newer versions of libraries and musl c. If I can get it to compile there, and on debian, I’m in good shape as far as compatibility goes. I used to really enjoy Arch and the rolling updates when I was younger, but I’ve gotten to where I don’t want to mess with things constantly changing.

      I use python venv for nearly everything I do python, and the way go is setup does make it extremely easy since it uses a per user environment anyway.