PROBLEM: the setup contains information that are misleading
We decided to allow the possibility to modify packages with local content such as:
-
parameters/
: with--set-parameters
-
drun.sh
: with--set-drun
-
dexplore.sh
: with--set-dexplore
And indeed these folder and files are stored in the package. So on the contrary to the source of the package which is stored in a version-controlled repo, the parameters volume which is mounted is the one that is holded in the package not the one in the repo.
So it needs to be clear that parameters
, drun.sh
and dexplore.sh
from the repo are all just exemples.
We took this decision to allow people that do not have write access to the repository to be able to modify the parameters anyway and experiment with it.
So far so good, However in the setup.json there are some informations like:
-
ParamPath
: the path in the repo to the parameters is used only to copy the parameters into the package at initialization. After the parameters have been modified this information is not relevant anymore. -
DRunPath
: the path in the repo to thedrun.sh
script -
DExplorePath
: the path in the repo to thedexplore.sh
script
Removing these variables from the setup.json
file would remove the misleading.
Can we do it?
So it is still required in the setup.toml
but it is not in the setup.json
.
Now the question is what about kufair package dump-setup
? It is supposed to generate a setup.toml
that is usable to create a comparative package.
The perfect solution would be:
setup.toml --> create package --> setup.json --> dump-setup --> setup.toml --> create same package!!
With entry and output being the same.