Reported by dikim on 16 Jul 2014 15:29 UTC
We may want to make oscar-packager a little smarter to do the following jobs:
Allow users to have their own config without overwriting the existing config files.
Developers may not need to touch the build.cfg file
For example, in order to let a developper avoid to edit oscar-packager config file, we would add a --localcontrib or equivalent to have oscar-packager look for /etc/oscar/oscar-packager/localcontrib{,opkgx}.cfg
thus on oscar-packager the std config files could be updated without overwriting the oscar developper own config files
Reported by dikim on 16 Jul 2014 15:29 UTC We may want to make oscar-packager a little smarter to do the following jobs:
For example, in order to let a developper avoid to edit oscar-packager config file, we would add a --localcontrib or equivalent to have oscar-packager look for /etc/oscar/oscar-packager/localcontrib{,opkgx}.cfg
thus on oscar-packager the std config files could be updated without overwriting the oscar developper own config files