Fully transparent and generic cache for config and app database

The existing caching mechanism for config files was abstracted and extended, so
that it could be re-used to parse and cache the info.yaml files. This results
in a much more robust application database and should get rid of 99.9% of all
the -r/--recreate-database option usages.

Change-Id: Ic37fcd3b0e55d481712d469b6e331b9c433a9c5d
Reviewed-by: Dominik Holland <dominik.holland@qt.io>

1 files changed, 3 insertions, 2 deletions

diff --git a/examples/applicationmanager/custom-appman/custom-appman.cpp b/examples/applicationmanager/custom-appman/custom-appman.cpp
index 45591130..c02e91c0 100644
--- a/examples/applicationmanager/custom-appman/custom-appman.cpp
+++ b/examples/applicationmanager/custom-appman/custom-appman.cpp
@@ -1,5 +1,6 @@
 /****************************************************************************
 **
+** Copyright (C) 2019 The Qt Company Ltd.
 ** Copyright (C) 2019 Luxoft Sweden AB
 ** Copyright (C) 2018 Pelagicore AG
 ** Contact: https://www.qt.io/licensing/
@@ -54,7 +55,7 @@
 #include <QtAppManCommon/global.h>
 #include <QtAppManCommon/logging.h>
 #include <QtAppManMain/main.h>
-#include <QtAppManMain/defaultconfiguration.h>
+#include <QtAppManMain/configuration.h>
 #include <QtAppManPackage/packageutilities.h>
 #include <QtAppManManager/sudo.h>
 
@@ -73,7 +74,7 @@ Q_DECL_EXPORT int main(int argc, char *argv[])
     try {
         Main a(argc, argv);
 
-        DefaultConfiguration cfg;
+        Configuration cfg;
         cfg.parse();
 
         a.setup(&cfg);