2023-12-11 20:09:56 +01:00
|
|
|
A brief guide to backward-incompatible changes
|
|
|
|
|
that are likely to break configurations or workflows
|
|
|
|
|
|
2023-12-11 21:18:28 +01:00
|
|
|
2023-07-13
|
|
|
|
|
|
|
|
|
|
* a significant re-arrangement of modules and services, which will
|
|
|
|
|
probably break any configuration written before this time. For a
|
|
|
|
|
detailed explanation, see
|
|
|
|
|
https://www.liminix.org/doc/configuration.html#modules
|
|
|
|
|
|
2023-12-11 20:09:56 +01:00
|
|
|
2023-12-10
|
|
|
|
|
|
|
|
|
|
* configurations (usually) need no longer import modules from
|
|
|
|
|
modules/outputs because devices are expected to do this instead. This
|
|
|
|
|
change is because the outputs that make sense in any given context are
|
|
|
|
|
usually a property of the device being installed onto.
|
|
|
|
|
|
|
|
|
|
2023-12-11
|
|
|
|
|
|
|
|
|
|
* rename outputs.flashimage to outputs.mtdimage (and also diskimage to
|
|
|
|
|
mbrimage). This change is made in the expectation that "fooimage" is
|
|
|
|
|
the name of an outputs that gloms together other filesystem-like
|
|
|
|
|
outputs with some kind of partition table - so we might in future have
|
|
|
|
|
gptimage or lvmimage or ubimage.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
