From: Maxime Devos <maximedevos@telenet.be>
To: Xinglu Chen <public@yoctocell.xyz>, 48962@debbugs.gnu.org
Subject: [bug#48962] [PATCH] gnu: password-store: Update to 1.7.4.
Date: Sat, 12 Jun 2021 17:32:28 +0200 [thread overview]
Message-ID: <a7d1548040e9578cd04dd69b427d0975aee6ab43.camel@telenet.be> (raw)
In-Reply-To: <5fca8e36733d89e119502d5b2c061a654211d6a5.1623443670.git.public@yoctocell.xyz>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
Xinglu Chen schreef op vr 11-06-2021 om 22:35 [+0200]:
> - (add-after 'install 'wrap-path
> - (lambda* (#:key inputs outputs #:allow-other-keys)
> - (let ((out (assoc-ref outputs "out"))
> - (path (map (lambda (pkg)
> - (string-append (assoc-ref inputs pkg) "/bin"))
> - '("coreutils" "getopt" "git" "gnupg" "qrencode"
> - "sed" "tree" "which" "wl-clipboard" "xclip"))))
> - (wrap-program (string-append out "/bin/pass")
> - `("PATH" ":" prefix (,(string-join path ":"))))
> - #t))))
Trailing #t in phases are not required anymore (the warning will disappear when
core-updates) is merged. You could follow up with a commit removing the #t.
> - #:make-flags (list "CC=gcc" (string-append "PREFIX=" %output)
> [...]
> + #:make-flags (list "CC=gcc" (string-append "PREFIX=" %output)
This should have been ,(string-append "CC=" (cc-for-target)) instead of "CC=gcc",
such that the cross-compiler is used when cross-compiling. (
(To test cross-compilation: ./pre-inst-env guix build --target=aarch64-linux-gnu
password-store).
Otherwise, I don't see any problems, but I haven't tested.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-06-14 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 20:35 [bug#48962] [PATCH] gnu: password-store: Update to 1.7.4 Xinglu Chen
2021-06-12 15:32 ` Maxime Devos [this message]
2021-06-12 20:43 ` bug#48962: " Nicolas Goaziou
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=a7d1548040e9578cd04dd69b427d0975aee6ab43.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=48962@debbugs.gnu.org \
--cc=public@yoctocell.xyz \
/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.