Oleg Pykhalov <go.wig...@gmail.com> writes: > Then could you add a flag Vladimir talked about and send a patch? ;-)
What about a separate package? E.g.
(define-public pinentry-emacs
(package
(inherit pinentry-tty)
(name "pinentry-emacs")
(inputs
`(("emacs" ,emacs)
,@(package-inputs pinentry-tty)))
(arguments
`(#:configure-flags '("--enable-pinentry-emacs")))
(description
"Pinentry provides a console and an Emacs interface that allows
users to
enter a passphrase when required by @code{gpg} or other software.")))
I haven't delved into packaging so far. I have read the manual but I'm
unsure about the best practice for local hacking.
I have set GUIX_PACKAGE_PATH=~/.guix-packages, then
> cp ~/.config/guix/latest/gnu/packages/gnupg.scm ~/.guix-packages/
> chmod +w ~/.guix-packages/
Then add the above the the file, plus a
#:use-module (gnu packages emacs)
at the beginning.
Now if I do
> guix package -s pinentry-emacs
guix package: warning: failed to load '(gnupg)':
no code for module (gnupg)
name: pinentry-emacs
version: 1.1.0
outputs: out
systems: x86_64-linux i686-linux armhf-linux aarch64-linux
mips64el-linux
dependencies: emacs-25.3 libassuan-2.5.1 libsecret-0.18.5
ncurses-6.0-20170930
+ pkg-config-0.29.2
location: /home/ambrevar/.guix-packages/gnupg.scm:991:2
homepage: https://gnupg.org/aegypten2/
license: GPL 2+
synopsis: GnuPG's interface to passphrase input
description: Pinentry provides a console and an Emacs interface that
allows users to enter a
+ passphrase when required by `gpg' or other software.
relevance: 4
Notive the error at th beginning:
guix package: warning: failed to load '(gnupg)':
no code for module (gnupg)
I don't understand this.
That said, is this the commended way to proceed? Or should I work from
a local checkout of guix? What about the value of GUIX_PACKAGE_PATH then?
--
Pierre Neidhardt
signature.asc
Description: PGP signature
