Hi Stefan-- On Fri 2017-05-12 12:37:03 +0200, Stefan Bühler wrote: > it would be nice to build and have packages for the gpg-wks-* tools. > > It seems there was already done some work in > > https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git/log/?h=dev/wks > > I rebased that commit to the experimental branch,
thanks for this work!
> modified some texts and added man pages.
It'd be great to get these manpages upstream.
> Upstream install gpg-wks-client to /usr/lib/gnupg/, but I moved it in
> the package to /usr/bin - I get that it was designed to be a backend
> tool for MUAs, but right now I guess most people installing it will have
> to use it manually.
I'm not so sure about diverging from upstream in our first introduction
of these tools in debian. If we do this, we're effectively committing
to this divergence forever (someone's going to write scripts that use
/usr/bin/gpg-wks-* and then get upset when we change it). and it means
that anyone who writes docs will have to have a different "how to do
this on debian" section from "how to do this on fedora" or whatever.
would you object to using your packaging but shipping in the
upstream-approved location? or is it worth convincing upstream to ship
these tools in /usr/bin instead?
--dkg
signature.asc
Description: PGP signature
