I haven't even bother to try to write any code to see if this is feasible, but anyway...
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. For the DSA example, such a script could (optionally?) move an incompatible config/network out of the way, while leaving all other settings untouched. Preserving e.g. wireless config has a lot of value. With the possibily to cancel the upgrade, it would even attempt an incomplete conversion. IMHO, the main reason we can't do automatic DSA conversion is because there will be failures. But this isn't critical if it is detected prior to upgrading. Just a few random thoughts. Since you are about to fundamentally improve sysupgrade anyway ;-) Bjørn _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
