You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of making package installs more restrictive. In order for the package to install, the author must have tested it on a firmware version and added that specific firmware version to a valid firmware version list. No longer will packages attempt to create file sets during the install process. This is an unfortunate change made necessary by the difficult recovery when the GUI presents a white screen since it is then impossible to access PackageManager.
You will be able to bypass valid version checks but only from the command line.
This also means that a package will not install on new versions until the author adds the new version to the list !!!!
The text was updated successfully, but these errors were encountered:
Hi Kevin,
Does this mean that we need to actively update a file containing the "tested on firmware version x"? And if so, wouldn't that mean that if somebody updates to the latest Victron VenusOS without updating the package (or when not having internet access), the package does not get reinstalled?
Yes, what you say is all true. This is mainly to prevent the GUI from crashing (white screen) so maybe if the package does not modify the GUI files, you don't need the valid versions file in the package.
I am in the process of making package installs more restrictive. In order for the package to install, the author must have tested it on a firmware version and added that specific firmware version to a valid firmware version list. No longer will packages attempt to create file sets during the install process. This is an unfortunate change made necessary by the difficult recovery when the GUI presents a white screen since it is then impossible to access PackageManager.
You will be able to bypass valid version checks but only from the command line.
This also means that a package will not install on new versions until the author adds the new version to the list !!!!
The text was updated successfully, but these errors were encountered: