...and yet, a vast majority of the instances where I see a go package hosted as "github.com/user/go-foobar", they are not using gopkg.in.
I'm w/ Dave on this one; except in very rare instances, this shouldn't be done (and even then, you should try find a way to avoid it). Also, in many ways, this is a side effect of github's insistence that all their users live within a flat namespace. (n.b. I once had Chris Wanstrath ask me which one feature I thought was missing from Github. I told him "global cross reference links". I should have said, "How about a hierarchical namespace?") t. On Sunday, December 24, 2017 at 4:40:43 AM UTC-8, Tamás Gulácsi wrote: > > gopkg.in forces me to have github.com/go-goracle/goracle to produce > gopkg.in/goracle.v2 as the import path. Seemed to be a little price for a > nice import path. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
