Replies: 3 comments
-
|
Update: made a PR for this in config: ublue-os/config#68 |
Beta Was this translation helpful? Give feedback.
-
|
Update: PR is basically done and the updater is now in a much better place. It's a lot more polished than the current update system (logging failed update scripts, notifying the user of updates, etc) and works quite reliably. All that the PR needs before merging is acknowledgement from reviewers and image maintainers |
Beta Was this translation helpful? Give feedback.
-
|
No more PR in config, currently waiting for the repo to moved to the ublue org, then I can make a PR in the bling repo |
Beta Was this translation helpful? Give feedback.
-
solves: ublue-os/config#63
I finally got around to writing up a new update system, and with the help of tulili I finally got a spec and container file. The software is mostly done, but there's still some stuff that needs to be figured out before we integrate:
Is there going to be a GUI? How will this be handled? Libadwaita app? Integrate into KDE/GNOME settings?
How do we handle system level updates vs user updates? Is there a way to say... update some things as the root user, and other as the normal user, say the user needs root to update rpm-ostree or has a rootful distrobox container and whatnot
How is this going to be integrated? Will it be pulled into the config repo? Or will it be integrated? Or will it be a submodule of some sort?
Also it would be nice to get some extra eyes on the update services, spec file, container file, and the overall project, as there hasn't been much review from others
https://github.com/gerblesh/ublue-updater
Beta Was this translation helpful? Give feedback.
All reactions