From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Cournoyer Subject: Re: Our package names should not include "github-com" Date: Sun, 15 Oct 2017 20:41:45 -0400 Message-ID: <87r2u37wl2.fsf@gmail.com> References: <20171013014334.17601.30718@vcs0.savannah.gnu.org> <20171013014344.D813E20338@vcs0.savannah.gnu.org> <87lgkfhszj.fsf_-_@netris.org> <20171013202425.GA22896@jasmine.lan> <87r2u6h738.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3tTc-0007D1-E2 for guix-devel@gnu.org; Sun, 15 Oct 2017 20:41:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3tTZ-0004UI-9Q for guix-devel@gnu.org; Sun, 15 Oct 2017 20:41:52 -0400 Received: from mail-io0-x235.google.com ([2607:f8b0:4001:c06::235]:47034) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e3tTZ-0004Tq-3g for guix-devel@gnu.org; Sun, 15 Oct 2017 20:41:49 -0400 Received: by mail-io0-x235.google.com with SMTP id 101so14285881ioj.3 for ; Sun, 15 Oct 2017 17:41:47 -0700 (PDT) In-Reply-To: <87r2u6h738.fsf@netris.org> (Mark H. Weaver's message of "Fri, 13 Oct 2017 21:05:31 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver Cc: guix-devel@gnu.org Hello! Mark H Weaver writes: > Hi Leo, > > Leo Famulari writes: > >> These packages are libraries written in the Go programming language. Go >> libraries are referred to by their "import path" [0], which is a string >> intended to uniquely identify a particular software implementation. >> >> As I wrote in the commentary on the go-build-system (part of the commit >> series being discussed), import paths are based on the URL of the >> software. A package hosted at https://github.com/leo/foo has an import >> path of 'github.com/leo/foo'. In Go, this is the library's name. >> >> These import paths are the sole mechanism by which Go software is >> uniquely referred to by humans and the Go compiler. It is even baked >> in to how dependencies are organized on disk. > > Thanks for the explanation. I find this very disturbing, but I > acknowledge that this lock-in is caused by Go itself, and that there's > probably not much that we can do about it. Oh well. I withdraw my > objection to these package names. > > Regards, > Mark > > >> [0] https://golang.org/doc/code.html#ImportPaths I just read that link, and while it's true that they recommend using the source repository domain as the base path of the library, it is by no mean an obligation, as noted: In practice you can choose any arbitrary path name, as long as it is unique to the standard library and greater Go ecosystem. I personally fail to see how using github.com gives much more uniqueness to a library name (especially since I expect that most go stuff would be hosted there) and find it equally disturbing. How hard would it be to go against this de facto standard? Maybe we could have a procedure that would strip any domain name from the libraries import paths? Maxim