One of the perks of daily driving GNOME OS Nightly is the ability to easily test merge requests for system components as a sysext.
Uncategorized
2
Beiträge
2
Kommentatoren
0
Aufrufe
-
One of the perks of daily driving GNOME OS Nightly is the ability to easily test merge requests for system components as a sysext. I tried it for the first time today, with this MR making the Do Not Disturb switch into a shiny new quick setting
Move do-not-disturb to quick settings (!3691) · Merge requests · GNOME / gnome-shell · GitLab
Add a new "Do Not Disturb" toggle to quick settings and remove the existing switch from the calendar popup. Closes:
GitLab (gitlab.gnome.org)
-
One of the perks of daily driving GNOME OS Nightly is the ability to easily test merge requests for system components as a sysext. I tried it for the first time today, with this MR making the Do Not Disturb switch into a shiny new quick setting
Move do-not-disturb to quick settings (!3691) · Merge requests · GNOME / gnome-shell · GitLab
Add a new "Do Not Disturb" toggle to quick settings and remove the existing switch from the calendar popup. Closes:
GitLab (gitlab.gnome.org)
@tbernard I wonder how good this workflow is for development. I'm a bit too used to have Qt and all KDE libraries compiled from source in a prefix and being able to just recompile the part I need and then restarting the shell/app to see the changes.
Can sysext be applied to a running system?
