Open jjkola opened 3 months ago
There is three options how to proceed with this:
Having the update JSON file in the main branch and keep it pointing to newest version.
Having the update JSON file in release branch
Having the update JSON file in separate place (updateJson would not point directly at source control)
I didn't understand the idea automatic updates
It is not automatic in the sense that it would update itself automatically but in the sense that package managers (for example mrepo) can read the update JSON file (with the help of updateJson property) to determine if there is a newer version available. I have been thinking about this and I think the best option would be to point outside of version control. This way it should be easy to point to the latest version regardless of the version used. This would also help version control as we don't need to keep release branches for ever and can prune old ones (tags can be used for returning to old version if needed, for example for bug checking).
chroot-distro should support updateJson property for module.prop file and the associated update JSON file. This makes updating to a new version easier as there is no need for the user to download the updated version separately.