gnupg2: don't preserve the old gpg2 executable name
authorBaruch Siach <baruch@tkos.co.il>
Tue, 14 Nov 2017 12:02:38 +0000 (14:02 +0200)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Mon, 27 Nov 2017 20:52:13 +0000 (21:52 +0100)
commit86dfb429ae1770550beb49299ef08ef05605c190
treed69bbcc2d1d9fd8b349e5feaededf27273548d5e
parent00012bf9d5943f007e0ae0e1e45ff6dab102e9d6
gnupg2: don't preserve the old gpg2 executable name

Commit e82fadab236a (gnupg2: bump to version 2.2.0) added a configure
option to keep the old 'gpg2' executable name to avoid conflict with the
gnupg package. It turns out that gnupg depends on !BR2_PACKAGE_GNUPG2
since commit 2cadb26e6d4 (gnupg: make gnupg and gnupg2 mutually
exclusive). Drop this configure option.

Rename the config option that controls the removal of gpgv2, now gpgv,
to match the new name. Add legacy config symbol handling.

Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Config.in.legacy
package/gnupg2/Config.in
package/gnupg2/gnupg2.mk