I am interested in keeping my (to be) OpenWRT installation up to date "automatically".
I read in forum that there is no auto-update feature and there are reasons for it. I stumbled across a long forum thread and in there I found a quote which I really liked:
Personally.... something like an RSS feed checkbox on RELEASE images, that displays a SECURITY FIX notification in LUCI.... ( which could possibly be extended to per device "autopatch" opt in scripts ) is enough from where I stand. If a user is unable to check this every few weeks / months and reflash / mitigate at an APPROPRIATE time of day, then they really shouldn't be flashing firmware - setting up services in the first place.
I'd really like that. Does something like that exist? Maybe there is a mailing list which sends out a message only once a new stable or security patch has been released? I have no problem with having to update and reinstall my packages manually. I am just looking for a way to get notified automatically.
Is there a machine readable "feed" which lists the current version (security patch) of OpenWRT?
I have snooped around a little and found some possible sources:
My ideal solution would be something where I can just enter my email address and whenever a new stable or security relevant release comes out it sends me a message.
You can receive release announcements via Discourse with the bell icon in the topic view for the Release and security announcement category (I use "Watching first post"), or you can sign up for the mailing list at https://lists.openwrt.org/mailman/listinfo/openwrt-announce.
if you have basic requirements (preferably also on a stable release)... you should now be able to leverage auc for all of the gruntwork which substantially reduces any code you'd need for this...
I am curious though. Is opkg development related to OpenWRT? The source seems separate but the package repo is hosted under an OpenWRT domain? Or is OpenWRT just mainting one (of many) openpkg repos? I assume the latter is the case.
is for non-core packages... where they are non-essential to basic router function and/or benefit from wider development input... ( it comes down to source management objectives and sharing )