#71 Seperate configs for papco_routines.save
When starting up, papco allows the option of seperate "configurations", i.e. different set of modules loaded.
For that there are seperate config directories that get set up under ~/papco_user, like "gps_config" etc. that then store their own versions of
papco_default.dat
papco_include_addins.pro
papco_include_modules.pro
papco_state
What is not done in a "per configuration" mode is starting papco from a compiled state - papco_routines.save is put under the main papco_user and loaded from there. This needs to be done seperately for each configuration.
Reason: I have cron jobs that do simple stuff in the papaco environment that need to load up fast - and loading up a pre-compiled version of papco is much faster than recompiling it each time the cron job runs (some get data from real-time sites that run every minute).