unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 50420-done@debbugs.gnu.org
Subject: [bug#50420] [PATCH 0/2] Add sendgmail.
Date: Thu, 23 Sep 2021 14:42:46 -0400	[thread overview]
Message-ID: <YUzKpoEo3Tzgwj42@jasmine.lan> (raw)
In-Reply-To: <899b1ee1-2223-8780-729f-ec06e793ad84@philipmcgrath.com>

On Thu, Sep 23, 2021 at 05:59:44AM -0400, Philip McGrath wrote:
> That would make sense to me: I'm not sure what the general rule is for
> breaking out of the language-specific naming conventions, and I'm not a Go
> programmer, but “go-github-com-google-gmail-oauth2-tools-go-sendgmail”
> seemed especially egregiously long.

In general, end-user applications (like a CLI program) can use a simple
name like 'sendgmail', which is what users expect.

Libraries, on the other hand, should use the long name. For Go, this
should match the "import path" of the program, with slashes changed to
hyphens, plus a "go-" prefix.

Internally to Go software, the "import path" is the true name of the
program:

https://golang.org/doc/gopath_code#ImportPaths

For example, there could be multiple Go libraries named 'sendgmail', but
Go software distinguishes them by including their network location in
the name.

We could invent another naming system, but Go naming is already so
complicated that I think it's worth trying to match the internal "import
path" names.




  reply	other threads:[~2021-09-23 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  5:36 [bug#50420] [PATCH 0/2] Add sendgmail Philip McGrath
2021-09-06  5:37 ` [bug#50420] [PATCH 1/2] gnu: Add go-cloud-google-com-go-compute-metadata Philip McGrath
2021-09-06  5:37   ` [bug#50420] [PATCH 2/2] gnu: Add go-github-com-google-gmail-oauth2-tools-go-sendgmail Philip McGrath
2021-09-14  9:32 ` bug#50420: [PATCH 0/2] Add sendgmail Ludovic Courtès
2021-09-23  9:59   ` [bug#50420] " Philip McGrath
2021-09-23 18:42     ` Leo Famulari [this message]
2021-09-23 19:40       ` Sarah Morgensen

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YUzKpoEo3Tzgwj42@jasmine.lan \
    --to=leo@famulari.name \
    --cc=50420-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=philip@philipmcgrath.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).