Handling Opinionated Programming Languages
Hello everyone,
How do you guys handle programming in languages that want to package imports "their" way? I'm mainly referring to things like Python, Golang, or Rust. I'm in the middle of a small Golang project and need to import a uuid library that guix doesn't package on it's own. I could make the package which isn't difficult but that leads me down the tension between "Go project is more portable if I use go get ..." vs "Project is more reproducible if I use Guix".
How do you all do it?
3 replies
@RumRunningDevil The usual method is with ‘guix import go --recursive’. (There are currently more than 2k Go packages in Guix that were created like this.)
Does that work for you?
Well you learn a new thing everyday. Looks like guix import would make building packages easier. This is a bit more a question about bridging the gap between how Go want's to handle its packages and how Guix wants to.
The ideal would be a setup that would allow me to declare a shell with a manifest and have it generate a go.mod out of the manifest in the process.
Appreciate the reply!
Package it in Guix and upstream it. Guix is one of the greater tools to take care dependecy mess (and ring reproducibiluty while it's at it)