That’s really helpful, Martin. It’s made me realise there are 23 Entware packages that have updates available. Up to now, I have never even looked at those packages, let alone update any. And I’m reluctant to update without knowing the implications. For example, I know that any Entware packages that Diversion needs will be updated automatically behind the scenes when Diversion updates.A sort of amtm usage help/self education page has been added to the website.
However, there are Entware packages that I know I use (even if infrequently) eg openssh-sftp-server and opkg. And there are packages I suspect I use but perhaps from within the other scripts and maybe from within Merlin’s firmware eg logrotate, syslog-ng and ntpd, which again I assume get updated with the relevant script.
So my question is: by manually updating all Entware packages, might I perhaps break one of the scripts by causing it to use a newer version of a package for which it might not yet be compatible, or is it safe to update all Entware packages regardless?