unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: help-debbugs@gnu.org (GNU bug Tracking System)
To: guix-patches@gnu.org
Subject: bug#43765: closed (Re: [bug#43766] [PATCH] gnu: Add go-github-com-errata-ai-vale.)
Date: Mon, 02 Nov 2020 13:54:02 +0000	[thread overview]
Message-ID: <handler.43765.D43766.160432520516331.notifdone@debbugs.gnu.org> (raw)
In-Reply-To: 20201002171317.1680-1-foo.dogsquared@gmail.com

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

Your bug report

#43766: [PATCH] gnu: Add go-github-com-errata-ai-vale.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 43765@debbugs.gnu.org.

-- 
43766: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43766
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

[-- Attachment #2: Type: message/rfc822, Size: 2652 bytes --]

From: "Ludovic Courtès" <ludo@gnu.org>
To: Gabriel Arazas <foo.dogsquared@gmail.com>
Cc: 43766-done@debbugs.gnu.org
Subject: Re: [bug#43766] [PATCH] gnu: Add go-github-com-errata-ai-vale.
Date: Mon, 02 Nov 2020 14:53:13 +0100
Message-ID: <87r1pblvau.fsf@gnu.org>

Hi,

Gabriel Arazas <foo.dogsquared@gmail.com> skribis:

> * gnu/packages/textutils.scm (go-github-com-errata-ai-vale): New variable.

Applied, thanks!

Ludo’.


[-- Attachment #3: Type: message/rfc822, Size: 5558 bytes --]

From: Gabriel Arazas <foo.dogsquared@gmail.com>
To: guix-patches@gnu.org
Subject: [PATCH] gnu: Add go-github-com-errata-ai-vale.
Date: Sat,  3 Oct 2020 01:13:16 +0800
Message-ID: <20201002171317.1680-1-foo.dogsquared@gmail.com>

One of my favorite writing tools and also my first dive into Go thru
packaging this program.
I do have a couple of questions/feedback regarding packaging Go packages:

* When do I add the missing dependencies? Is it required or just a
preference? Are indirect dependencies included to be listed?
I noticed that some of the Go packages have incomplete
depedencies on the package definition and you can still build the
Go packages even if you remove it (or at least my package does that).

* I feel like there's a missing section in the documentation
regarding naming Go packages since I noticed there are some
inconsistencies. For example, there are packages that starts with 'go-github.com'
and 'go-github-com'. (To be fair, I only found like 2 packages that has
different naming so far.)





      parent reply	other threads:[~2020-11-02 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 17:13 [bug#43765] [PATCH] gnu: Add go-github-com-errata-ai-vale Gabriel Arazas
2020-10-02 17:13 ` [bug#43766] " Gabriel Arazas
2020-11-02 13:53   ` bug#43766: " Ludovic Courtès
2020-11-02 13:54   ` bug#43766: closed (Re: [bug#43766] [PATCH] gnu: Add go-github-com-errata-ai-vale.) GNU bug Tracking System
2020-11-02 13:54 ` GNU bug Tracking System [this message]

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=handler.43765.D43766.160432520516331.notifdone@debbugs.gnu.org \
    --to=help-debbugs@gnu.org \
    --cc=43765@debbugs.gnu.org \
    --cc=guix-patches@gnu.org \
    /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).