Go Packaging Proposal Process

Re:Go Packaging Proposal Process by mmkx on Friday July 29, 2016 @09:14AM (#12186569)

This is needed badly. I am a huge Golang advocate, but I refuse to use the "github.com" package naming/folder setup mess. It's just not elegant.

[ Parent | on HN ]

Re:Go Packaging Proposal Process by jvehent on Friday July 29, 2016 @09:15AM (#12186577)

Projects I care about use a domain I control. It's not that hard to setup: https://jve.linuxwall.info/blog/index.php?post/2015/08/26/Ho...

We even do it with just an S3 bucket for go.mozilla.org: https://go.mozilla.org/

[ Parent | on HN ]

Re:Go Packaging Proposal Process by mfer on Friday July 29, 2016 @09:28AM (#12186642)

I'm a fan of that as well. Had not considered using S3 for that. Do you know of a good writeup for handling "?go-get=1" paths differently from html paths in S3? I should likely know this but a quick pointer would be helpful.

[ Parent | on HN ]

Re:Go Packaging Proposal Process by jvehent on Friday July 29, 2016 @09:39AM (#12186702)

I have not looked into this.

The S3 method is kinda experimental. It works for first-level packages but fails for nested packages. We need to look into setting up redirects for those.

The best way to do this yourself is to run an instance of https://github.com/niemeyer/gopkg, but that's not #serverless anymore ;)

[ Parent | on HN ]

Re:Go Packaging Proposal Process by dlsniper on Friday July 29, 2016 @09:30AM (#12186645)

You spelled Go incorrectly.

[ Parent | on HN ]