Am 01.11.24 um 16:09 schrieb Michael Catanzaro:
On Fri, Nov 1 2024 at 03:13:21 PM +01:00:00, Leon Fauster via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I had the impression that globally installed configurations
(e.g. /etc/dconf/db/local.d/) should be "committed" with
# dconf update
No, don't do this. For the same reason you never package dconf
overrides, you also never mess with dconf in packaging. You only
interact with gsettings, not with dconf.
All you need to do is install the gsettings override. It's easy. :)
Example: https://src.fedoraproject.org/rpms/ptyxis/tree/rawhide
Ok, thanks. Following questions arised here now:
- An explanation, why its bad would bring some light into this.
- ibus.el9 package do package a dconf file + scriptlet (its here
installed, didn't check the whole repo)
- I mainly use etc/dconf because locking is possible.
gsettings override seem not to offer such feature, or does it?
- overrides should also be "committed" with ... or not?
# glib-compile-schemas /usr/share/glib-2.0/schemas
I only ask so that I can do the right thing, thanks ...
BTW, two perspectives here: packaging in general,
or for local customization via "custom rpm" or any
other way of automation ...
--
Leon
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
