Why did you name it _3mux and not 3mux like in upstream?

Thank you @filalex77!

I just tagged 3mux as v0.1.0 so feel free to update the derivation to use that version. Now that it's tagged, is the -unstable suffix still recommended?

I'd also love to be added as a maintainer of this derivation (nixpkgs user aaronjanse).

Why did you name it _3mux and not 3mux like in upstream?

Afaik, a Nix identifier cannot start with a numeral. The package nixos._1password does the same thing.

@aaronjanse Thank you for checking in! I will update it to the tag (and drop the unstable suffix), and also add you as a maintainer.

I also updated 3mux to use go modules before tagging v0.1.0. Should this derivation be updated to use buildGoModule?

@aaronjanse Great, thanks for letting me know! Yes, using buildGoModule is much better, as we don't need to maintain separate deps.nix file. I'll do that :)

Sorry, I just published some major bug fixes to tag v0.1.1. From now on, 3mux should be much more stable (I've created a dev branch!).

Would you mind quickly updating this derivation to v0.1.1? No dependencies have changed.

EDIT: v0.2.0

I guess the darwin build should be skipped once it gets a build slot, since it is marked as broken.

GutHub, you're drunk..
I pressed squash, got this:

Reloaded the page and it was merged, but what the..:

So it created a merge commit and renamed it to the commit message I had entered, but did not use the commit description I had entered and did not squash.