On 05/06/2020 09:27, Bjørn Mork wrote:
I wonder if there might be more flexible and user-friendly ways to handle upgrade incompatibilities if we are allowed to use code/metadata from the new image in the sysupgrade process? Instead of just providing a version number with some simple semantics like you describe, the new image could provide a script snippet or similar which codifies a more precise description of the incompatibility. And even a solution, if there is one.
A message (or URL?) might be nice, yes. That's not something we have right now...
For the DSA example, such a script could (optionally?) move an incompatible config/network out of the way, while leaving all other
That's typically a job offloaded to /etc/uci-defaults/* from the new image, isn't it? There's a lot of ar71xx -> ath79 handling done that way already...
Downgrades are, of course, unsupported. They could be, but it would waste precious flash, it makes more sense to warn users to backup beforehand in the LuCI interface (and not mess with sysupgrade itself, which needs to be able to **safely** work unattended as well).
-- Henrique de Moraes Holschuh _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
