searchidx: fix Xapian version comparison

We must use Perl v-strings consistently on both sides of the
comparison.  Fortunately, this was merely a no-op and didn't
cause any data integrity problems (aside from increased wear on
the storage device).

Fixes: c25c66af0a8a (searchidx: use vstring to improve readability, 2023-04-07)

diff --git a/lib/PublicInbox/SearchIdx.pm b/lib/PublicInbox/SearchIdx.pm
index 1cbf6d235a16a53646c9cb04cc39d4a9d031f7d8..d3a7a0c0867af13fcdd7aeff10786360edd1bb49 100644 (file)
--- a/lib/PublicInbox/SearchIdx.pm
+++ b/lib/PublicInbox/SearchIdx.pm
@@ -119,7 +119,7 @@ sub load_xapian_writable () {
        my $ver = eval 'v'.join('.', eval($xap.'::major_version()'),
                                eval($xap.'::minor_version()'),
                                eval($xap.'::revision()'));
-       if ($ver ge 1.4) { # new flags in Xapian 1.4
+       if ($ver ge v1.4) { # new flags in Xapian 1.4
                $DB_NO_SYNC = 0x4;
                $DB_DANGEROUS = 0x10;
        }