From: Danny Milosavljevic <dannym@scratchpost.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 27260@debbugs.gnu.org
Subject: bug#27260: [PATCH] gnu: Add qgpgme.
Date: Tue, 6 Jun 2017 13:07:28 +0200 [thread overview]
Message-ID: <20170606130728.43bd08f0@scratchpost.org> (raw)
In-Reply-To: <1496699013-25966-1-git-send-email-h.goebel@crazy-compilers.com>
Hi Hartmut,
On Mon, 5 Jun 2017 23:43:33 +0200
Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> * gnu/packages/gnupg.scm (qgpgme): New variable.
> ---
> gnu/packages/gnupg.scm | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
> index c2b0278..30d5744 100644
> --- a/gnu/packages/gnupg.scm
> +++ b/gnu/packages/gnupg.scm
> @@ -407,6 +407,34 @@ instead. This way bug fixes or improvements can be done at a central place
> and every application benefits from this.")
> (license license:lgpl2.1+)))
>
> +(define-public qgpgme
> + (package
> + (inherit gpgme)
> + (name "qgpgme")
> + (arguments
> + `(#:phases
> + (modify-phases %standard-phases
> + (add-before 'build 'chdir-and-symlink
> + (lambda* (#:key inputs #:allow-other-keys)
> + (let ((gpgme (assoc-ref inputs "gpgme")))
> + (symlink (string-append gpgme "/lib/libgpgmepp.la")
> + "lang/cpp/src/libgpgmepp.la")
> + (symlink (string-append gpgme "/lib/libgpgme.la")
> + "src/libgpgme.la"))
> + (chdir "lang/qt"))))))
Nice!
Please end the phase in #t.
Otherwise LGTM!
next prev parent reply other threads:[~2017-06-06 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 21:43 bug#27260: [PATCH] gnu: Add qgpgme Hartmut Goebel
2017-06-05 21:52 ` bug#27260: Note: the official name is "QGpgME" Hartmut Goebel
2017-06-06 11:07 ` Danny Milosavljevic [this message]
2017-06-06 12:04 ` bug#27260: [PATCH] gnu: Add qgpgme Hartmut Goebel
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=20170606130728.43bd08f0@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=27260@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).