gpgme @1.7.0: use deactivate hack for kdepimlibs4

[ryandesign (Ryan Carsten Schmidt)]

kdepimlibs4 depends on gpgme, but gpgme @1.7.0 and later installs header files that used to be installed by kdepimlibs4 @4.14.3_3 and earlier. So gpgme should use the deactivate hack to ensure kdepimlibs4 @4.14.3_3 or earlier is deactivated before attempting to activate gpgme @1.7.0 or later. Otherwise, you get this problem:

$ sudo port upgrade kdepimlibs4
--->  Computing dependencies for gpgme
--->  Fetching archive for gpgme
--->  Attempting to fetch gpgme-1.7.0_0+universal.darwin_15.i386-x86_64.tbz2 from https://packages.macports.org/gpgme
--->  Fetching distfiles for gpgme
--->  Verifying checksums for gpgme
--->  Extracting gpgme
--->  Applying patches to gpgme
--->  Configuring gpgme
--->  Building gpgme
--->  Staging gpgme into destroot
--->  Installing gpgme @1.7.0_0+universal
--->  Cleaning gpgme
--->  Computing dependencies for gpgme
--->  Deactivating gpgme @1.6.0_2+universal
--->  Activating gpgme @1.7.0_0+universal
Error: Failed to activate gpgme: Image error: /opt/local/include/gpgme++/configuration.h is being used by the active kdepimlibs4 port.  Please deactivate this port first, or use 'port -f activate gpgme' to force the activation.
Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_devel_gpgme/gpgme/main.log for details.
--->  Computing dependencies for kdepimlibs4
--->  Dependencies to be installed: gpgme
Error: Requested variants "" do not match those the build was started with: "+universal".
Error: Please use the same variants again, or run 'port clean gpgme' first to remove the existing partially completed build.
Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_devel_gpgme/gpgme/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

[dbevans (David B. Evans)]

Can vercmp properly compare versions that include a revision number? Or is there something else that needs to be done?

[dbevans (David B. Evans)]

Replying to devans@…:

Can vercmp properly compare versions that include a revision number? Or is there something else that needs to be done?

Nevermind, I figured it out myself. Answer is no, vercmp only looks at the version part. So need to compare revision separately (index 2 of $installed in the example).

[dbevans (David B. Evans)]

r153575