Skip to content
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

[Request] Migrate gsettings schema to org.buddiesofbudgie.magpie #7

Closed
eatyourbaby opened this issue Aug 12, 2023 · 2 comments
Closed
Labels
enhancement New feature or request v0 Related to Magpie v0 (Mutter fork)

Comments

@eatyourbaby
Copy link

Magpie version

0.9.2

Use-cases

Magpie currently shares the same gsettings schema namespace as mutter, i.e. org.gnome.mutter. However, if magpie were to co-exist with mutter in an installation, a newer (or older) version of mutter may no longer share the same keys with mutter 43, which might break magpie.

This also offers a solution to #3, as we can add the xrandr fractional scaling patch to magpie as a whole on any distribution.

Proposal

Migrate gsettings schema away from org.gnome.mutter to org.buddiesofbudgie.magpie.

References

No response

@serebit serebit added enhancement New feature or request v0 Related to Magpie v0 (Mutter fork) labels Aug 20, 2023
@fossfreedom
Copy link
Contributor

https://github.com/search?q=org%3ABuddiesOfBudgie%20%22org.gnome.mutter%22&type=code

Thats the sort of change required.

Making a global change like this also will impact other stuff like gnome-remote-desktop that quite a lot of people use.

I haven't look at potentially other GNOME dependencies - need to example gnome-settings-daemon and gnome-session and probably quite a few others as well.

@eatyourbaby
Copy link
Author

I just learned that Budgie to moving its configuration to TOML. I suppose this won't be an issue when magpie 1.0 releases then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v0 Related to Magpie v0 (Mutter fork)
Projects
None yet
Development

No branches or pull requests

3 participants