-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The state of the go packages #976
Comments
I'm not the maintainer of
@mmatongo: can you have a look at it ? |
I keep forgetting to do this for some reason, I'll send two PR's in a bit. |
Fixed, thanks. |
@aabacchus -- maybe poke @git-bruh -- maybe poke The others are either wontfix or ignored -- I suppose we should just consider it a lost cause. Maintainers are probably welcome to vendor dependencies themselves and point |
Does anyone more familiar with GitHub actions want to have a go at this? makew0rld/amfora#296 (comment) |
by the way, the maintainer of aerc said they don't want the "burden" of vendoring deps in tarballs. |
Some(well, all of them except dnscrypt-proxy) go packages still use internet connection to fetch dependencies. This is bad because only kiss itself should be allowed(we should really enforce this via unshare) to fetch something from internet. We should use
go build -mod=vendor
where possible, and if not possible - convince upstream to add support for it.GOFLAGS='-mod=vendor'
GOFLAGS='-mod=vendor'
GOFLAGS='-mod=vendor'
FUCK YOU GOOGLE!The text was updated successfully, but these errors were encountered: