EDIT: Fixed in current version

@Zarbod, unfortunately it seems they only support go1.17 for now. Hopefully they update it in the recent future.

I get this error whenever I try to install using yay

../../src/github.com/Psiphon-Labs/psiphon-tunnel-core/vendor/github.com/Psiphon-Labs/quic-go/internal/qtls/go118.go:5:13: cannot use "quic-go doesn't build on Go 1.18 yet." (untyped string constant) as int value in variable declaration

upstream is supporting go 1.17 now. I updated the package and it seems to be working properly now

That's research you'll have to embark upon youself. :)

Surely upstream has some issue tracker somewhere... or some sort of forum/mailing list.

Pestering upstream is not possible in this case. They don't accept issues in their repo, so I assume when they have availability they will update their go version. Regarding taking directly their binary, yes, this is for sure possible. @ainola you mention the possibility of sourcing an old release of go from the aur, would this be possible without the user having to uninstall the current version?

The first order of business would be to pester upstream to make their software work with 1.16. If they refuse, you'll need to source an older release of Go on the AUR or make it yourself if absent.

The idea of package management in general is to coordinate packages together with a defined, cohesive system; Docker is a very unfit solution as it stomps all over Arch build systems with who-knows-what is defined in the Dockerfile.

If you just want this to be installable on Arch, I'd recommend creating psiphon-tunnel-core-bin-git and installing the pre-built binaries.

I hope that clarifies the situation.

@ainola is it possible to use a different go version in a chroot environment? wouldn't this be more or less equivalent regarding computing resources to the docker approach?

Docker is definitely not going to fly here. I'd end up either reverting or deleting the package. Packages in the AUR need to be built from either the base system or a chroot environment.

@ainola I thing I finished all your recomendations, thank you :) Now I found a bigger issue, it seems this package only works if compiled with go 1.14, as there is an embedded (and customized dependency, quic-go) that has not been updated and doesn't work with go 1.15+... So the only way I see to make it work is to revert to docker... what do you think?