unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Building gpgme with Qt support?
Date: Sun, 04 Jun 2017 19:52:27 -0400	[thread overview]
Message-ID: <87d1aj71l0.fsf@netris.org> (raw)
In-Reply-To: <20170604183540.GA2840@jasmine> (Leo Famulari's message of "Sun, 4 Jun 2017 14:35:40 -0400")

Leo Famulari <leo@famulari.name> writes:

> On Sun, Jun 04, 2017 at 08:23:56PM +0200, Hartmut Goebel wrote:
>> Hi,
>> 
>> since version 1.7 gpgme [1] includes both the C++ bindings (former
>> package: gpgmepp) and the Qt-Framework API (former package qgpgme, not
>> in guix).
>> 
>> Our gpgme package is currently build *without* support for Qt:
>> 
>> checking for GPGME_QT... checking for GPGME_QTTEST... ./configure: line 18672: : command not found
>> configure: WARNING:
>> ***
>> *** Qt5 (Qt5Core) not found Qt Binding will be disabled.
>> ***
>> 
>> The major draw-back of adding these bindings is that this would install
>> qtcore (and all it's dependencies) for any application using gpgme.
>> 
>> How can we avoid this?
>
> Could we make a new package qt-gpgme that inherits from gpgme and provides a
> QT-enabled gpgme??

If there's a need for Qt-enabled gpgme, then I think this is the right
approach.  I feel strongly that our primary gpgme package should *not*
depend on Qt.

     Thanks,
       Mark

  reply	other threads:[~2017-06-04 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 18:23 Building gpgme with Qt support? Hartmut Goebel
2017-06-04 18:35 ` Leo Famulari
2017-06-04 23:52   ` Mark H Weaver [this message]
2017-06-05 10:26   ` Hartmut Goebel
2017-06-05 13:21     ` Danny Milosavljevic
2017-06-05 21:47       ` 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=87d1aj71l0.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).