summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* common: Add missing G_BEGIN/END_DECLSwip/issue-23Christian Persch2021-03-033-0/+12
| | | | Fixes: https://gitlab.gnome.org/GNOME/dconf/-/issues/23
* Merge branch 'increment/0.39.2' into 'master'Daniel Playfair Cal2021-02-071-1/+1
|\ | | | | | | | | build: increment version following 0.39.1 release See merge request GNOME/dconf!66
| * build: increment version following 0.39.1 releaseincrement/0.39.2Daniel Playfair Cal2021-02-081-1/+1
|/
* Merge branch 'changelog/0.39.1' into 'master'0.39.1Daniel Playfair Cal2021-02-071-0/+10
|\ | | | | | | | | chore: update NEWS for 0.39.1 See merge request GNOME/dconf!65
| * chore: update NEWS for 0.39.1changelog/0.39.1Daniel Playfair Cal2021-02-081-0/+10
|/
* Merge branch 'wip/smcv/systemd-unit' into 'master'Daniel Playfair Cal2021-02-075-0/+33
|\ | | | | | | | | | | | | service: Add a systemd unit for D-Bus activation Closes #24 See merge request GNOME/dconf!63
| * service: Add a systemd unit for D-Bus activationSimon McVittie2021-02-085-0/+33
|/ | | | | | | | | | | | | | | | 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>
* Merge branch 'completion' into 'master'Philip Withnall2021-01-081-3/+3
|\ | | | | | | | | Minor fixes to bash completion script See merge request GNOME/dconf!64
| * completion: Add missing commands to completion listPhilip Withnall2021-01-081-3/+3
| | | | | | | | | | | | | | The `list-locks` and `blame` commands were missing in the completion script. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
| * completion: Drop nonexistent lock and unlock commands from completionPhilip Withnall2021-01-081-2/+2
|/ | | | Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
* Merge branch 'patch/engine-check' into 'master'Daniel Playfair Cal2020-12-199-43/+318
|\ | | | | | | | | Engine: Do not emit optimistic change notifications unless the local value is different See merge request GNOME/dconf!2
| * engine: remove spurious local change notificationsDaniel Playfair Cal2020-12-192-5/+241
| | | | | | | | | | | | | | | | | | | | 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).
| * engine: seal the in_flight queue before sending itDaniel Playfair Cal2020-12-191-0/+1
| | | | | | | | | | It would be wrong to change the in_flight queue, so seal it to ensure that it is consistently sealed.
| * common: factor out dconf_gvdb_utils_table_from_changesetDaniel Playfair Cal2020-12-192-2/+12
| |
| * common: factor out dconf_gvdb_utils_changeset_from_tableDaniel Playfair Cal2020-12-192-27/+36
| |
| * move dconf-gvdb-utils from service into commonDaniel Playfair Cal2020-12-195-9/+9
| |
| * client: add symbol mapDaniel Playfair Cal2020-12-192-0/+19
|/ | | | | | | 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.
* Merge branch 'fix-symbols' into 'master'Daniel Playfair Cal2020-12-199-68/+121
|\ | | | | | | | | build: Improve libdconf visible symbols See merge request GNOME/dconf!59
| * include symbols needed by GNU BFD ld in mapDaniel Playfair Cal2020-12-192-0/+4
| | | | | | | | | | | | | | 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.
| * build: Remove libdconf-common-hiddenIñigo Martínez2020-12-193-21/+16
| | | | | | | | | | | | | | | | | | | | | | `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.
| * build: Improve libdconf visible symbolsIñigo Martínez2020-12-192-7/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`.
| * client: add abicheckDaniel Playfair Cal2020-12-192-1/+42
| |
| * tests: factor out abicheck from gsettingsDaniel Playfair Cal2020-12-195-40/+52
|/ | | | This will allow it to be used for other binaries
* Merge branch 'increment/0.39.1' into 'master'Daniel Playfair Cal2020-09-131-1/+1
|\ | | | | | | | | Increment version number for 0.39 unstable series See merge request GNOME/dconf!62
| * increment version number following 0.38.0 releaseDaniel Playfair Cal2020-09-131-1/+1
|/
* Merge branch 'release/0.38.0' into 'master'0.38.0Daniel Playfair Cal2020-09-132-1/+7
|\ | | | | | | | | Release 0.38.0 See merge request GNOME/dconf!61
| * update NEWS file for 0.38.0 releaseDaniel Playfair Cal2020-09-131-0/+6
| |
| * Increment version number for 0.38.0 releaseDaniel Playfair Cal2020-09-131-1/+1
|/
* bin/completion/dconf: Add compile to autocompleteAndreas Polnas2020-07-151-2/+2
| | | | | | | | | | | | | | | 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>
* Merge branch 'wip/jtojnar/bash-completion-prefix' into 'master'Daniel Playfair Cal2020-05-041-2/+6
|\ | | | | | | | | build: Install bash-completion relative to datadir See merge request GNOME/dconf!58
| * build: Install bash-completion relative to datadirJan Tojnar2020-04-161-2/+6
|/ | | | | | | | | | | | | | 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>
* Increment version number following 0.36 releaseMarek Kasik2020-03-101-1/+1
|
* Prepare 0.36 release0.36.0dconf-0.36Marek Kasik2020-03-102-1/+6
|
* Merge branch 'prepare/0.35.1' into 'master'Daniel Playfair Cal2020-01-062-1/+14
|\ | | | | | | | | Release 0.35.1 See merge request GNOME/dconf!57
| * Increment version number post 0.35.1 releaseDaniel Playfair Cal2020-01-061-1/+1
| |
| * Update NEWS for 0.35.1 release0.35.1Daniel Playfair Cal2020-01-061-0/+13
|/
* Merge branch 'patch/service-check' into 'master'Daniel Playfair Cal2019-12-306-26/+449
|\ | | | | | | | | Service: only emit changed signals when values change See merge request GNOME/dconf!3
| * Service: avoid redundant writes even after other non redundant writes have ↵Daniel Playfair Cal2019-12-293-2/+69
| | | | | | | | succeeded
| * Service: add tests exercising new functionality to avoid redundant writesDaniel Playfair Cal2019-12-291-0/+139
| |
| * Changeset: factor out some memory management from test_filter_changesDaniel Playfair Cal2019-12-291-56/+27
| |
| * Changeset: make dconf_changeset_filter_changes filter out key/path resets ↵Daniel Playfair Cal2019-12-292-17/+90
| | | | | | | | when appropriate
| * Service: Add unit tests for dconf_changeset_filter_changesDaniel Playfair Cal2019-12-291-0/+126
| |
| * Service: filter changesets when performing writes such that changed events ↵Daniel Playfair Cal2019-12-293-25/+72
|/ | | | are only emitted if new values differ from existing values
* Merge branch 'diegoe_fix-meson-0.52' into 'master'Daniel Playfair Cal2019-11-071-1/+1
|\ | | | | | | | | | | | | build: Update use of link_whole for meson-0.52 Closes #59 See merge request GNOME/dconf!54
| * build: Update use of link_whole for meson-0.52Diego Escalante Urrelo2019-11-061-1/+1
|/ | | | | | | | | | | | | 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
* gsettings: Update abicheck.sh scriptDiego Escalante Urrelo2019-11-051-1/+23
| | | | | | | | | | | 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
* build: Drop redundant `install` key from `configure_file()`Philip Withnall2019-11-051-1/+0
| | | | | | | | | 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
* Increment version number following 0.34 releaseDaniel Playfair Cal2019-09-101-1/+1
|
* Prepare 0.34 release0.34.0dconf-0.34Daniel Playfair Cal2019-09-101-1/+1
|
* Increment version number following 0.33.2 releaseDaniel Playfair Cal2019-08-201-1/+1
|
View Lorry Controller Status