How to preserve plugins across minor upgrades
Posted: Wed Aug 28, 2019 7:33 am
I'm looking for a way to keep the installed plugins enabled (and their configuration preserved) across minor upgrades.
I often rebuild Gargoyle with an updated OpenWrt-18.06 branch to benefit from kernel updates on that branch [1]. I'd like to do automated minor upgrades between these updated versions of Gargoyle 1.11.X.
Right now, it appears that after an upgrade, the plugins are disabled but still installed. In order to reactivate them, I need to uninstall, reinstall, and then manually reconfigure them; which is what I want to get rid of.
In most cases, I'd expect the installed plugins to continue to work after a sysupgrade despite not updating the plugins at the same time (the plugins I use, ddns and openvpn, have no kernel dependencies); but if necessary, I'd update them along with the system image. I have a local plugin repository available over HTTP, but I could copy the updated plugin IPKs to the router as part of my automated process as well.
Would it be sufficient to have a bunch of /lib/upgrade/keep.d files that preserve a few strategically important files to keep installed plugins intact?
Any other ideas?
Thanks!
[1] https://github.com/openwrt/openwrt/comm ... nwrt-18.06
I often rebuild Gargoyle with an updated OpenWrt-18.06 branch to benefit from kernel updates on that branch [1]. I'd like to do automated minor upgrades between these updated versions of Gargoyle 1.11.X.
Right now, it appears that after an upgrade, the plugins are disabled but still installed. In order to reactivate them, I need to uninstall, reinstall, and then manually reconfigure them; which is what I want to get rid of.
In most cases, I'd expect the installed plugins to continue to work after a sysupgrade despite not updating the plugins at the same time (the plugins I use, ddns and openvpn, have no kernel dependencies); but if necessary, I'd update them along with the system image. I have a local plugin repository available over HTTP, but I could copy the updated plugin IPKs to the router as part of my automated process as well.
Would it be sufficient to have a bunch of /lib/upgrade/keep.d files that preserve a few strategically important files to keep installed plugins intact?
Any other ideas?
Thanks!
[1] https://github.com/openwrt/openwrt/comm ... nwrt-18.06