unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Martin Becze <mjbecze@riseup.net>, 47769@debbugs.gnu.org
Subject: [bug#47769] [PATCH 5/6] gnu: Added go-github-com-google-gousb.
Date: Wed, 14 Apr 2021 23:31:31 +0200	[thread overview]
Message-ID: <fce2be2309a7677bfad305ed9ed5379e2b9fee21.camel@telenet.be> (raw)
In-Reply-To: <20210414102010.6100-5-mjbecze@riseup.net>

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

On Wed, 2021-04-14 at 05:20 -0500, Martin Becze wrote:
> +(define-public go-github-com-google-gousb
> +  (package
> +    (name "go-github-com-google-gousb")
> +    (version "2.1.0")
> +    (source
> +     (origin
> +       (method git-fetch)
> +       (uri (git-reference
> +             (url "https://github.com/google/gousb.git")
> +             (commit (string-append "v" version))))
> +       (sha256
> +        (base32
> +         "1aki6hk009sicrf7gxy5nkjmj4j7lsy0by4kjgd9bwq8ragfyv5x"))
> +       (file-name (git-file-name name version))))
> +    (build-system go-build-system)
> +    (arguments
> +     '(#:import-path "github.com/google/gousb"))
> +    (propagated-inputs
> +     `(("pkg-config" ,pkg-config)
> +       ("libusb" ,libusb)))

Most likely, "pkg-config" should be in native-inputs.

I believe there's a linter that checks whether packages should
be in native-inputs, but I'm not sure if pkg-config is detected.
Consider running ./pre-inst-env guix lint go-github-com-google-gousb.

Also, why is "libusb" in "propagated-inputs" and not in "inputs"?
"inputs" is usually preferred over "propagated-inputs", but there
are valid reasons to use "propagated-inputs" instead.

Greetings,
Maime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-04-14 21:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 10:14 [bug#47769] [PATCH 0/6] Add wally-cli Martin Becze
2021-04-14 10:20 ` [bug#47769] [PATCH 1/6] gnu: Add go-gopkg-in-cheggaaa-pb-v1 Martin Becze
2021-04-14 10:20   ` [bug#47769] [PATCH 2/6] gnu: Added go-github-com-logrusorgru-aurora Martin Becze
2021-04-14 10:20   ` [bug#47769] [PATCH 3/6] gnu: Added go-github-com-caarlos0-spin Martin Becze
2021-04-14 21:55     ` Nicolò Balzarotti
2021-04-15 12:59       ` Martin Becze
2021-04-15 14:57         ` Nicolò Balzarotti
2021-04-14 10:20   ` [bug#47769] [PATCH 4/6] gnu: Added go-github-com-marcinbor85-gohex Martin Becze
2021-04-14 10:20   ` [bug#47769] [PATCH 5/6] gnu: Added go-github-com-google-gousb Martin Becze
2021-04-14 21:31     ` Maxime Devos [this message]
2021-04-14 10:20   ` [bug#47769] [PATCH 6/6] gnu: Added wally-cli Martin Becze
2021-04-14 21:28     ` Maxime Devos
2021-04-14 22:02       ` Nicolò Balzarotti
2021-04-15 13:11         ` Martin Becze
2021-04-15 13:44           ` Nicolò Balzarotti
2024-03-29 14:27 ` bug#47769: [PATCH 0/6] Add wally-cli Sharlatan Hellseher

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=fce2be2309a7677bfad305ed9ed5379e2b9fee21.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=47769@debbugs.gnu.org \
    --cc=mjbecze@riseup.net \
    /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).