ASU, only add requested packages to default set

[oxwivi]

Continuing the discussion from OpenWrt 23.05.0 - First stable release:

@patrakov

Let's say that the upgrade complains about bind-dig not being available. You click the red near it, as well as near any other unwanted packages, and retry.

However, this will still leave you with the version of wpad linked against wolfssl - i.e. not the current recommendation of using mbedtls. You can either fix this manually, or just remove the bad wpad and add the good one to the package list.

I'm very new to Attended Sysupgrade (learned about it yesterday), So I understand from your comment, it will warn me when a package I've currently installed is not available to select from the newer version, and that's great. But the part about wpad concerns me; is it not possible to mark a few packages that I want to be constant, while the base packages can be whatever is the default for he version? For example, I want luci-app-https-dns-proxy every time I upgrade, but I don't want to concern myself if OW is switching from wolfssl to openssl or anything else so as to let it run with minimum intervention and configuration from me, the user.

Also, is it possible to have the other two options that are shown in the default firmware flashing UI?

[patrakov]

The official viewpoint seems to be:

• Library switching only happens when upgrading between major OpenWrt releases.
• Attended sysupgrade is therefore OK between minor releases (e.g., 23.05.0 -> 23.05.2) and will not hit this problem.
• Attended sysupgrade is not recommended anyway between major releases (22.03.5 -> 23.05.2). Please do a regular sysupgrade to the default image and reinstall what's missing, picking up the new defaults.

[oxwivi]

I guess that makes sense, but then it would not be applicable to non-techies as I was hoping for. Then again, if I was hoping for non-techies to easily keep their routers up-to-date, Attended Sysupgrade is much too advanced and unnecessary. Maybe a much simpler tool that just gets the latest image for a given board, no custom build or anything, and just upgrade. But another counterpoint would be some custom setup necessary for a given scenario, maybe extra packages are necessary, so this hypothetical tool wouldn't cover it...

Does OW's sysupgrade tool allow for running scripts post-upgrade? Then the hypothetical tool that only flashes standard image can be used, and then rest of the packages can be installed after the restart

I still think that the option to do as I described in OP to be useful. That would make sense for major updates, along with a large warning to go read release notes in case there are large changes regarding flagged packages, if they're at all available in the new version.