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 11:28 AM, Simon McVittie <s...@debian.org> wrote: > 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. For instance in > <https://github.com/peterbourgon/diskv/blob/master/index.go>: > > > import ( > > "sync" > > > > "github.com/google/btree" <<--- > > ) > > I'm not defending that design decision, but given that it exists, > having Debian package names mechanically derived from what you "import" > (or "use" or whatever the language's idiom is) seems like A Good Thing. > See also: the way we encode SONAMEs into C binary package names, and > the name you "import" or "use" into Python and Perl binary package names > ("import dbus.mainloop.qt" -> python3-dbus.mainloop.qt, > "use Text::Markdown::Discount" -> libtext-markdown-discount-perl) > > S > > -- :wq
