ccm-purge: add support for selectable database backends

ccm-purge was still assuming that the profile data was being stored in
GDBM. This updates the call to use the correct EDG::WP4::CCM::DB
indirection to handle all backends.

This fixes quattor#14 on github.

src/main/bin/ccm-purge

@@ -28,6 +28,7 @@ use GDBM_File;
 use Errno qw(ESRCH EPERM);
 use File::Path;
 use EDG::WP4::CCM::CCfg qw(initCfg);
+use EDG::WP4::CCM::DB;
 
 #
 # Global Variables
@@ -279,9 +280,9 @@ sub save_active_urls($) {
     # delete($NonactiveURL{$md5});
 
     # search URLs in fetch porperties
-
-    tie(%hash, "GDBM_File", "${CacheDir}/${profile}/eid2data.db", GDBM_READER,
-        0640) or die("${CacheDir}/${profile}/eid2data.db failed to open: $!");
+    my $readErr = EDG::WP4::CCM::DB::read(\%hash,
+                                          "${CacheDir}/${profile}/eid2data");
+    die("Failed to read eid2data: $readErr") if defined($readErr);
 
     foreach $key ( keys(%hash) ) {
         $ukey = unpack("L", $key);