Bjørn Lie
e1dec2d463
- split gtk-docs from -devel package, these are not needed during building projects using glib2 - use _multibuild as the meson buildprocess is very awkward regarding the documentation - builds single-jobs only and twice (again during %install). This way the rest of distribution waiting for glib2-devel to be available is not blocked by this OBS-URL: https://build.opensuse.org/request/show/958100 OBS-URL: https://build.opensuse.org/package/show/GNOME:Factory/glib2?expand=0&rev=471 |
||
|---|---|---|
| _multibuild | ||
| .gitattributes | ||
| .gitignore | ||
| baselibs.conf | ||
| glib2-bgo569829-gettext-gkeyfile.patch | ||
| glib2-dbus-socket-path.patch | ||
| glib2-fate300461-gettext-gkeyfile-suse.patch | ||
| glib2-gdbus-codegen-version.patch | ||
| glib2-rpmlintrc | ||
| glib2-suppress-schema-deprecated-path-warning.patch | ||
| glib2-upstream-gnome_defaults.conf | ||
| glib2.changes | ||
| glib2.csh | ||
| glib2.sh | ||
| glib2.spec | ||
| glib-2.70.4.tar.xz | ||
| gsettings.zsh | ||
| macros.glib2 | ||
| README.Gsettings-overrides | ||
Quoting the "Vendor overrides" section from [1]: Default values are defined in the schemas that get installed by an application. Sometimes, it is necessary for a vendor or distributor to adjust these defaults. Since patching the XML source for the schema is inconvenient and error-prone, glib-compile-schemas reads so-called 'vendor override' files. These are keyfiles in the same directory as the XML schema sources which can override default values. The schema id serves as the group name in the key file, and the values are expected in serialized GVariant form, as in the following example: [org.gtk.Example] key1='string' key2=1.5 glib-compile-schemas expects schema files to have the extension .gschema.override [1] http://developer.gnome.org/gio/stable/GSettings.html