Gustavo Arnosti Neves

[Version 0.3.4](https://github.com/tavinus/opkg-upgrade/releases/tag/0.3.4) was pushed. Any feedback would be appreciated. ## v0.3.4 : - [x] Load info from `/etc/openwrt_release` when available - [x] Add more router info on email report (from...

Thanks for the snippet. Since this is busybox/ash there is no `tput` to use (by default). There is also no simple way to test if colors are available and I...

My preferred solution would be to have a single bash var inside a config file that could be sourced by the main program. Seems easy enough, could be an array...

Also, we need to create a `default list` of those problematic packages, but that can be tricky as well. Different versions and archs may have different lists, which will add...

I guess we should just use `uci` for the config. Makes more sense and is a lot more powerful. https://openwrt.org/docs/guide-user/base-system/uci This way we just use `uci` to add/read/etc the config...

Yep. That is on the wish-list. For now, I need to understand how exactly opkg behaves related to that. I THINK it will create `/etc/config/*-opkg` when the new config files...

Hi. This is interesting. First question is if changing from `/etc/openwrt_release` to `/etc/os-release` will change anything. Will it be exactly the same info in the reports or is anything gonna...

This is from the help of pdfscale: ``` --install, --self-install [target-path] Install itself to [target-path] or /usr/local/bin/pdfscale if not specified Should contain the full path with the desired executable name...

**BTW** Both the installer and the upgrader can certainly be simplified a lot just by assuming/ensuring that we are running as root. So we can basically make a single check...

That is on the wishlist (self-update). I was even thinking about that yesterday, but the fact that SSL is not always present does not help. I will probably not make...