Closed gerblesh closed 1 year ago
on second thought it may be better to build it here, though idk tbf, there's ups and downs to each approach
To be honest considering this is a Universal Blue project, having it inside the org in some way would be interesting. Including this project inside this container would also not require a whole container to be built just for the updater, and instead just include it to ours!
What do you think? Maybe could be a good idea!
After going over it with akdev, it's probably best just to keep the rpm in the repo for CI, PRs, etc. We can either pull it in from the fetch script when we get releases working with an RPM or we can pull it in from the container, either way works, currently it pulls from the container, but that could change once rpm releases are added
The repo is now in the uBlue org too, why I waited to do this PR https://github.com/ublue-os/ublue-update
Oh! Great! I'll merge it now then :>
added in the ublue-update RPM into the rpms folder, may want to include something about uninstalling the update services, or include something in startingpoint that enables this by default.