From: Leo Famulari <leo@famulari.name>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Our package names should not include "github-com"
Date: Mon, 16 Oct 2017 17:38:43 -0400 [thread overview]
Message-ID: <20171016213843.GB20802@jasmine.lan> (raw)
In-Reply-To: <87r2u37wl2.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
On Sun, Oct 15, 2017 at 08:41:45PM -0400, Maxim Cournoyer wrote:
> >> [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?
Using the domain name as part of the *upstream* library name is useful
for upstream authors because of how Go's built-in dependency management
tools work. Go integrates dependency management into the language and
the `go` tool itself. Re-using the upstream library name is useful
because they have already disambiguated for us.
I don't intend to be rude, but I'm not going to put much effort into
responding to further comments that are not based on knowledge of how Go
handles package / dependency management with its built-in tools, or
modular programming in Go, in general. Already I used tons of my free
time to learn this stuff, just so I could make Guix packages of Go
software. Please meet me where I am.
Again, I don't see an ethical problem here, so any motivation for me to
participate in this discussion, as a volunteer, must be technical. If
it's *wrong* to name the packages in this way, I will behave
differently.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-16 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171013014334.17601.30718@vcs0.savannah.gnu.org>
[not found] ` <20171013014344.D813E20338@vcs0.savannah.gnu.org>
2017-10-13 17:12 ` Our package names should not include "github-com" Mark H Weaver
2017-10-13 17:41 ` ng0
2017-10-13 17:44 ` ng0
2017-10-13 20:24 ` Leo Famulari
2017-10-14 1:05 ` Mark H Weaver
2017-10-16 0:41 ` Maxim Cournoyer
2017-10-16 21:38 ` Leo Famulari [this message]
2017-10-17 10:44 ` Leo Famulari
2017-10-18 2:09 ` Maxim Cournoyer
2017-10-16 13:05 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171016213843.GB20802@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.