Be more careful with config file inclusion

We can't really do the basedir magic from db-functions as it is just being
sourced and is not the currently executing script. Although a bit
repetitive, it is a lot safer to just include the config file everywhere.

Noticed this when trying to run the latest available scripts on sigurd.

Signed-off-by: Dan McGee <dan@archlinux.org>

1 files changed, 1 insertions, 0 deletions

diff --git a/cron-jobs/createFileLists b/cron-jobs/createFileLists
index 345f9aa..d936853 100755
--- a/cron-jobs/createFileLists
+++ b/cron-jobs/createFileLists
@@ -5,6 +5,7 @@ targetdir=$reposdir
 repos="core extra testing community"
 
 . "$(dirname $0)/../db-functions"
+. "$(dirname $0)/../config"
 
 if [ -f "/tmp/createFileList.lock" ]; then
     echo "Error: createFileList allready in progress."