-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Switch from dconf to gschema-overrides #1716
chore: Switch from dconf to gschema-overrides #1716
Conversation
I removed `gdm` profile because it's already present in `/usr/share/dconf/profile`. I removed touchpad tap-to-click setting, because it's already the default since Gnome 46 (next GTS will be on Gnome 46). I removed `user` profile because it's already present in `/etc/dconf/profile/`. I moved dconfs from `local.d` to `distro.d`, as that's recommended to do as a distribution/custom image maintainer. `local.d` is intended for local-users, so let's make that easier for them. Relocatable schemas & locked settings are not supported in gschema-overrides, hence why they remained in dconf. I commented the gschema override, to make it easier to see where relocatable schemas are located. `gsettings list-relocatable-schemas` can be used to check those. We use `zz0-` prefix for gschema override, so that we can assure that Fedora gschema-override defaults won't override Bluefins. Downstreams can use `zz1-`, `zz2-`, `zz3-`, etc. prefix, like I recommend BlueBuild users to do so. Gschema overrides can be checked in build-time for errors in case some keys get migrated or someone makes an unintentional typing mistake, where dconf ones can't. So let's utilize that to our advantage. Bluefin should work without problems, but I'll have to additionally test Aurora, to see how Ptyxis dconfs are handled there.
Tested Aurora, it works great |
Those 2 extensions miss gschema xml, hence the reason why gschema overrides doesn't work for them. This is fixable, but not by me.
Tested & fixed remaining Bluefin settings, everything works! This is ready to merge |
What happens to existing gts users if this merges right now? |
They'll have this setting off by default Unless the user manually toggled off, then on that setting, which is very unlikely |
Ok what about leaving it in for now but leaving a comment like |
No problem, I'll add it back |
Added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did a local image build of bluefin (not aurora) with these changes. Nothing sticks out to me as problematic.
And as I mentioned in Discord, I'm using the same general approach in my custom image, too. So this seems like a fair change to me.
Great idea, I merged that PR, ready to go! |
@castrojo Ready! |
- See ublue-os/bluefin#1716 - Rename our gschema overrides to match convention
What I did
I removed
gdm
profile because it's already present in/usr/share/dconf/profile/
.I removed touchpad tap-to-click setting, because it's already the default since Gnome 46 (next GTS will be on Gnome 46).
I removed
user
profile because it's already present in/etc/dconf/profile/
.I moved dconfs from
local.d
todistro.d
, as that's recommended to do as a distribution/custom image maintainer.local.d
is intended for local-users, so let's make that easier for them.Relocatable schemas & locked settings are not supported in gschema-overrides, hence why they remained in dconf.
I commented the gschema override, to make it easier to see where relocatable schemas are located.
gsettings list-relocatable-schemas
can be used to check those on booted system.We use
zz0-
prefix for gschema override, so that we can assure that Fedora gschema-override defaults won't override Bluefins. Downstreams can usezz1-
,zz2-
,zz3-
, etc. prefix, like I recommend BlueBuild users to do so.Gschema overrides can be checked in build-time for errors in case some keys get migrated or someone makes an unintentional typing mistake, where dconf ones can't. So let's utilize that to our advantage.
Testing
Bluefin should work without problems, but I'll have to additionally test Aurora, to see how Ptyxis dconfs are handled there.