James

> default.nix and shell.nix (and maybe even a flake.nix) to the root of the project Not allergic to it AFAICT. I don't know enough about nix. If the files *need*...

> #!/usr/bin/env bash > some projects refuse to do this, if your not adverse to it , i can make a PR. I'll make you a deal... Once the go...

> it's just nix weirdness We can always add a new build target for nix if needed. But maybe try setting GOPATH to something totally writable and see if that...

@dantefromhell I'd like to apologize for not replying earlier. I haven't been receiving github notifications. It's a bug they had once with my mailserver but it is apparently back. If...

@dantefromhell I quite recentl updated a bunch of go mod stuff so everything builds again. This is coincidentally around the exact same time you made your comment AFAICT. LMK if...

@urandom2 You're saying getting a newly tagged release would be helpful to the nix folks? Please confirm, and then sure, I can do that. Is there anything else in the...

> generally nix is a special case, so I do not want you to bend over backwards to support us. Propose anything that you think makes sense. If I don't...

> After fixing up the mgmt make scripts , from !/bin/bash to !/usr/bin/env bash Send patches for this if you want. Also -i stuff I think it's deprecated now. HTH

> the "fix" I am proposing is to generate code just like you are today, but remove the .gitignore lines and check those files in. I understood, and while it...

Perhaps you have a 32 bit machine, and golang doesn't have an int64 on that (or at least not in the struct?) I don't know, but if you dig some...