| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
chore: update NEWS for 0.39.1
See merge request GNOME/dconf!65
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
service: Add a systemd unit for D-Bus activation
Closes #24
See merge request GNOME/dconf!63
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On systems using systemd --user and
dbus-daemon --session --systemd-activation, this means that dconf
is correctly placed in its own cgroup, instead of being part of
dbus.service's cgroup. This allows it to be controlled by
systemctl --user, have resource limits set and so on.
On other systems (in particular those where systemd is not used at all),
the SystemdService field is ignored and dbus-daemon will continue to
start dconf-service as its own child process ("traditional activation"),
making this change harmless to apply.
Resolves: https://gitlab.gnome.org/GNOME/dconf/-/issues/24
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|\
| |
| |
| |
| | |
Minor fixes to bash completion script
See merge request GNOME/dconf!64
|
| |
| |
| |
| |
| |
| |
| | |
The `list-locks` and `blame` commands were missing in the
completion script.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|/
|
|
| |
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|\
| |
| |
| |
| | |
Engine: Do not emit optimistic change notifications unless the local value is different
See merge request GNOME/dconf!2
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When used with the "fast" (optimistic concurrency) API, the engine library
emits a change notification local to a process after a change is initiated
from that process. Previously, it would emit this notification even if the
newly written value was the same as the previous value (according to that
process's view of the state). After this change, the local change
notification is not sent unless the new value is different from the
current value (as seen by that process).
|
| |
| |
| |
| |
| | |
It would be wrong to change the in_flight queue, so seal it to ensure
that it is consistently sealed.
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
| |
This is similar to what is done in in libdconfsettings to prevent
symbols not part of the API from being available in the compiled
binaries. In practice, this makes it possible to include more code in
the common directory without creating new symbols in libdconf.
|
|\
| |
| |
| |
| | |
build: Improve libdconf visible symbols
See merge request GNOME/dconf!59
|
| |
| |
| |
| |
| |
| |
| | |
On FreeBSD using the default GNU BFD linker, the use of --version-script
fails unless the symbols `__progname` and `environ` are included. This
change includes them in the symbol map, which should allow the build to
succeed on FreeBSD.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`libdconf-common-hidden` is built to hide symbols not necessary
in the `gsettings` gio module that only needs to expose
`g_io_module_[load|query|unload]` symbols.
To achieve this a symbol map along with `version-script` linker flag
is used. Thanks to this only the necessary symbols are exposed,
building `libdconf-common-hidden` static library is not necessary
anymore and the existing dependencies can be used.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
One of the changes in c50f3758d3e5da4f8b244227b211c3c3f454275c that
was part of the GNOME/dconf!11 merge request, removed the list of
libraries `libdconf` linked with. This was overlooked because meson
build files used the same `deps` variable in several files and this
make `libdconf` library function to use dependencies from
`gsettings` library. Due to this, only `dconf_client_*` symbols
where visible in `libdconf`.
The set of libraries to link with in `libdconf` has been restored so
now all the necessary symbols are visible again.
The `link_whole` parameter in both `libdconf_client_dep` and
`libdconf_common_dep` has been changed back to `link_with`.
|
| | |
|
|/
|
|
| |
This will allow it to be used for other binaries
|
|\
| |
| |
| |
| | |
Increment version number for 0.39 unstable series
See merge request GNOME/dconf!62
|
|/ |
|
|\
| |
| |
| |
| | |
Release 0.38.0
See merge request GNOME/dconf!61
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While working with Dconf I noticed in the bash CLI
I was unable to autocomplete when typing "dconf compile"
This fix will make it so the user is able to auto complete
the compile option in bash.
I have tested it on my Manjaro and PopOS! machines
and it's working expected.
As this is my first contribution please look twice so I have
not missed anything.
Signed-off-by: Andreas Polnas <andreas.polnas93@hotmail.com>
|
|\
| |
| |
| |
| | |
build: Install bash-completion relative to datadir
See merge request GNOME/dconf!58
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since bash-completion 2.9, it was no longer possible to override
the completionsdir through prefix. [1] In 2.10, the overridability
was re-estabilished but this time through datadir variable. [2]
This should not really matter except for developers installing the project
into a custom prefix or distros using per-package prefixes like NixOS.
[1]: https://github.com/scop/bash-completion/commit/81ba2c7e7dfbaefbafa1e8615727c9612e5fb314
[2]: https://github.com/scop/bash-completion/pull/344
Co-Authored-By: Iñigo Martínez <inigomartinez@gmail.com>
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Release 0.35.1
See merge request GNOME/dconf!57
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Service: only emit changed signals when values change
See merge request GNOME/dconf!3
|
| |
| |
| |
| | |
succeeded
|
| | |
|
| | |
|
| |
| |
| |
| | |
when appropriate
|
| | |
|
|/
|
|
| |
are only emitted if new values differ from existing values
|
|\
| |
| |
| |
| |
| |
| | |
build: Update use of link_whole for meson-0.52
Closes #59
See merge request GNOME/dconf!54
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
A regression in meson-0.52 caused uses of link_whole to expose scenarios
where duplicate symbols issues could appear. In particular
libdconf_client_dep was being link_whole'd to itself, which recursively
already included libdconf_common which was also a link_whole.
This change does not modify the available symbols in libdconf.so, and is
compatible with meson-0.52 and 0.51.
See: https://github.com/mesonbuild/meson/pull/6030
Fixes: https://gitlab.gnome.org/GNOME/dconf/issues/59
|
|
|
|
|
|
|
|
|
|
|
| |
gcc-9 is including `mangle_path` in the symbols of
gsettings/libdconfsettings.so when building with support for gcov
(--coverage). This means that our ignored symbols had to be updated.
Update abicheck.sh so the test suite passes again. Also include a
comment to explain the above and how the test works.
Fixes: https://gitlab.gnome.org/GNOME/dconf/issues/60
|
|
|
|
|
|
|
|
|
| |
When `install_dir` is set, `install` defaults to true, so there’s no
need to set it manually. This fixes a Meson warning.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
Closes: #57
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Fix dbus leaks
See merge request GNOME/dconf!51
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change fixes the dbus-leak tests by dropping the cached
GDBusConnection objects references when the bus connection is closed.
The issue was introduced with recent changes made to GLib[1]
where invoking g_test_dbus_down() will fail after a
timeout if the GDBusConnection object for the session bus leaks.
Given g_test_dbus_down() will first close the connection before checking
for leaks unreffing the object when the connection is closed should fix
the issue.
[1] https://gitlab.gnome.org/GNOME/glib/merge_requests/963
Signed-off-by: Andre Moreira Magalhaes <andre@endlessm.com>
|