Re: golang naming scheme

2016-06-07 Thread Tollef Fog Heen
]] Russ Allbery > That's one of the reasons why so many people use github, since that URL is > less likely to change. > > One interesting detail of this approach is that it means that a takeover > of the package by a different maintainer results in a different package > name inherently. I'm

Re: golang naming scheme

2016-03-31 Thread Martín Ferrari
On 31/03/16 19:18, Russ Allbery wrote: >>> If I understand correctly, the URL of a Go package is ABI. > That's one of the reasons why so many people use github, since that URL is > less likely to change. > > One interesting detail of this approach is that it means that a takeover > of the

Re: golang naming scheme

2016-03-31 Thread Vincent Bernat
❦ 31 mars 2016 15:22 -0400, Holger Levsen  : >> That's one of the reasons why so many people use github, since that URL is >> less likely to change. > > less likely, but imagine 3000 golang packages in the archive in 5 years and > then github is bought by google and

Re: golang naming scheme

2016-03-31 Thread Holger Levsen
Hi, I guess this shall be my last mail on this topic. On Thu, Mar 31, 2016 at 11:18:11AM -0700, Russ Allbery wrote: > That's one of the reasons why so many people use github, since that URL is > less likely to change. less likely, but imagine 3000 golang packages in the archive in 5 years and

Re: golang naming scheme

2016-03-31 Thread Russ Allbery
Holger Levsen writes: > On Thu, Mar 31, 2016 at 04:28:56PM +0100, Simon McVittie wrote: >> If I understand correctly, the URL of a Go package is ABI. > OMG. URLs never change. All people have a middle name which can be > encoded in UTF-8. > Thanks for explaining. That's

Re: golang naming scheme (was: re Bug#819591: ITP: golang-github-peterbourgon-diskv)

2016-03-31 Thread Holger Levsen
On Thu, Mar 31, 2016 at 04:28:56PM +0100, Simon McVittie wrote: > If I understand correctly, the URL of a Go package is ABI. OMG. URLs never change. All people have a middle name which can be encoded in UTF-8. Thanks for explaining. -- cheers, Holger, somewhat speechless about modern

Re: golang naming scheme (was: re Bug#819591: ITP: golang-github-peterbourgon-diskv)

2016-03-31 Thread Paul R. Tagliamonte
That's correct. This is no different than saying the Python importable name is the package name. And why we see stuff like: python-foo.bar, since you import foo.bar. You import that URL. The package name is just the import name. No different than Python. Cheers, Paul On Thu, Mar 31, 2016 at

Re: golang naming scheme (was: re Bug#819591: ITP: golang-github-peterbourgon-diskv)

2016-03-31 Thread Paul Tagliamonte
Also, I take issue with calling this "lazyness". To imply the golang team hasn't put thought into a large section of the archive is not very nice. Thanks, Paul On Thu, Mar 31, 2016 at 11:34 AM, Paul R. Tagliamonte wrote: > That's correct. > > This is no different than

Re: golang naming scheme (was: re Bug#819591: ITP: golang-github-peterbourgon-diskv)

2016-03-31 Thread Simon McVittie
On Thu, 31 Mar 2016 at 11:10:56 -0400, Holger Levsen wrote: > As you might have noticed, golang packages seem to have an, aehm, > interesting naming scheme, where they basically take the upstream URL > and turn this into a package name. If I understand correctly, the URL of a Go package is ABI.

golang naming scheme (was: re Bug#819591: ITP: golang-github-peterbourgon-diskv)

2016-03-31 Thread Holger Levsen
Hi, this is not about this package, but rather about the general golang naming scheme. This ITP just triggered me to finally speak up… On Thu, Mar 31, 2016 at 09:23:07AM +1100, Dmitry Smirnov wrote: >Package name: golang-github-peterbourgon-diskv > URL: https://gith