On Wednesday, 14 May 2025 08:03:19 BST Simon Josefsson wrote: > What's missing for me is to build and install the > tools in some usable way. What system are you using, and which packages > did you have to build and how did you install them? It was hard for me > to get anything to work on a Debian-derived distribution
I use Slackware. I build my own packages for all GnuPG stuff (libgpg-error, libassuan, libgcrypt, gnupg, etc.) and use them instead of the system-provided packages, so that I can always use the latest version (and apply patches when needed). Slackware makes it very easy to do things like that, but I am not sure how easy it would be to do something similar on a Debian-based system. Debian packaging is, well, a thing in itself. If you don’t mind installing programs that are not under the control of your system’s package manager, another option is to build and install an entire GnuPG stack *in parallel* to your system-managed one, somewhere under /usr/local (or even somewhere in your own home directory if you don’t want to mess with your system at all). The “speedo.mk” build script (in gnupg’s build-aux directory) comes in very handy for that, try running `make -f build-aux/speedo.mk help` for details. > because they ship a GnuPG fork that interacts badly with genuine GnuPG. o_O - Damien
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
