On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler <m...@adrianschmutzler.de> wrote: > > Just a quick one: > > > > So, no matter what we do, there is no easy way forward. > > > > We could remove all ar71xx -> ath79 migration helper scripts, ar71xx > > board names from supported devices lists in ath79 images and make the > > target a brand new, without any concerns about soon-to-be obsolete ar71xx ;) > > At the moment, I'm actually mostly inclined towards this solution. > > However, for me personally SUPPORTED_DEVICES was always more a "don't brick > entirely" flag, so I never expected it to ensure 100 % config compatibility. > More like preventing me from flashing ubnt,unifi image onto > tplink,wdr-4300-v1. This impression might have been wrong, though. > > But as mentioned by Ansuel, there are other incompatible switches to come > (and some are already waiting), and unless we want to create new targets or > rename devices in these cases, we have to think about different "levels" of > compatibility anyway beyond ar71xx->ath79.
Wouldn't it be reasonable to put up a warning that migrating from ar71xx->ath79 will require a reset of networking configuration? Then all you need to do is detect when that sort of upgrade is occurring and nuke the requisite files. Also I don't know bout y'all, but I usually take a major revision upgrade as an opportunity to hard reset and rebuild anyways. (Years of ingrained ddwrt habits) > > Best > > Adrian > > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
