pinentry-tqt for the trinity desktop (former KDE3/Qt3 code)
Damien Goutte-Gattat
dgouttegattat at incenp.org
Sun Oct 29 11:43:15 CET 2017
On 10/29/2017 05:47 AM, deloptes wrote:
> 1. I get following error:
Strange, I don't get that error. Maybe we're using a slightly different
version of TQt3...
> => removing hasMarkedText (as it is flagged obsolete) solves the problem
OK.
>
> 2. Compile still failed with: > [...]
> => creating version.texi in doc solves the problem and packages are build
> correctly
Are you building directly from a Git checkout? Then you need to call the
configure script with --enable-maintainer-mode. And you should also call
the the autogen.sh script before that.
To test building a package I would suggest creating first a proper tarball:
$ ./autogen.sh
$ ./configure --enable-maintainer-mode
$ make
$ make distcheck
This will create a tarball that you should be able to use in your
packaging script as if it came directly from GnuPG upstream.
> 3. How we can set pinentry-tqt to default?
As far as I know the current build system has no option to explicitly
set the default pinentry. The default pinentry is automatically selected
among the enabled pinentries, using a hardcoded preference order.
Since we're adding a new pinentry, I have put it at the end of the
preference list, so it will never be selected as the default unless all
other pinentries are disabled. I don't want to change that without prior
approval from other pinentry developers.
Making a pinentry the default simply means installing a symlink from
$prefix/bin/pinentry to the selected pinentry. So if you're building a
package for TDE, where it makes perfect sense to use pinentry-tqt as the
default, I would suggest that in your packaging script, you remove the
symlink created by pinentry's "make install" and replace it by your own
symlink to pinentry-tqt.
Damien
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20171029/761bc886/attachment.sig>
More information about the Gnupg-devel
mailing list