Hi Jim, On Oct 30, 2013, at 10:13 AM, Jim Meyering <j...@meyering.net> wrote: > On Tue, Oct 29, 2013 at 1:21 PM, Gary V. Vaughan <g...@gnu.org> wrote: >> for now the new tag and fallback to --short-log fixes all >> the immediate problems I was having (except the reliance on gnupg-1.4 >> gpgv). > > You say that as if there were a problem with the maint.mk rule. > The rule relies on the existence of a program named "gpgv". If your > distribution or packaging tool chooses to call that binary gpgv2,
Well, gnupg-2.0.22 itself chooses to call that binary gpgv2, which is why I reported it, because I imagine many other maintainers use a distro that ships gnupg-2.x rather that gnupg-1.4.x by default. > I encourage you simply to create (early in your path) a symlink mapping > the version-dependent name to the "right" one. Making the names of > such tools depend on the package version is not sustainable, and I'm > reluctant to make the rule accommodate it. Apple confounds me even more by shipping gnupg2, but without even a gpgv2 binary, so I have to build gnupg-1.4 anyway. My original report was inspired by the idea that most GNU maintainers would want to use the latest gnupg release, in which case the canonical name really is gpgv2. I have no strong feelings about it though; as long I've raised the issue, I know gnulib is making an informed decision on how to deal with it. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)
signature.asc
Description: Message signed with OpenPGP using GPGMail
