GNU bug report logs -
#47769
[PATCH 0/6] Add wally-cli
Previous Next
Reported by: Martin Becze <mjbecze <at> riseup.net>
Date: Wed, 14 Apr 2021 10:15:02 UTC
Severity: normal
Tags: patch
Done: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
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.
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 1 year and 54 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.