When switching from cooker 1.2.0 to 1.3.0 while using the same .cookerconfig-file (i.e. being in a work-dir which has been cooker initialized) an error occurs because the newly introduced (config)-option sstate-dir is not present in .cookerconfig.
To allow migration from one version of the cookerconfig-file to another it might be useful to have an API-version field inside. In that way a new version of cooker could migrate cookerconfig-file the first time it sees it.
When switching from cooker 1.2.0 to 1.3.0 while using the same .cookerconfig-file (i.e. being in a work-dir which has been cooker initialized) an error occurs because the newly introduced (config)-option
sstate-diris not present in.cookerconfig.To allow migration from one version of the cookerconfig-file to another it might be useful to have an API-version field inside. In that way a new version of cooker could migrate cookerconfig-file the first time it sees it.