Keep multipython dependencies reproducible (nighty CI? separate project?)
BornAgain's forthcoming multipackage configuration (#96 (closed)) depends on Python libs that are currently maintained in /home/build/multiphonon on our Debian build server. They need to be touched only when a new Python minor version comes out.
In my opinion this introduces a risk for severe trouble in some distant future. External dependencies may change; knowledge may be lost. I suggest to put the build scripts into a separate project that includes a CI script that is rerun every night.
Also, for the sake of keeping BornAgain truly open source, it is absolutely necessary that external developers can easily rebuild the entire thing.
Edited by Wuttke, Joachim