| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
meson does not allow to build source code inside the source code
tree, for this reason there is no need for .gitignore files to
ignore built files.
This patch removes .gitignore files which are no longer needed.
https://bugzilla.gnome.org/show_bug.cgi?id=784910
|
|
|
|
|
|
|
| |
To avoid the burden of maintaining multiple build systems, this
patch removes autotools support.
https://bugzilla.gnome.org/show_bug.cgi?id=784910
|
|
|
|
|
|
|
|
| |
meson is a build system focused on speed an ease of use, which
helps speeding up the software development. This patch adds meson
support along autotools.
https://bugzilla.gnome.org/show_bug.cgi?id=784910
|
|
|
|
|
|
|
|
|
| |
This API has never appeared in a released version of dconf (even
unstable). Replace it with a more generally-useful form.
Update the test cases, dconf commandline tool and vapi accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=759128
|
|
|
|
|
|
| |
Add a -d option to 'dconf read' to read the default value.
https://bugzilla.gnome.org/show_bug.cgi?id=758864
|
|
|
|
|
|
|
| |
Add a list-locks command to the dconf commandline tool to list the locks
that are present in the current configuration.
https://bugzilla.gnome.org/show_bug.cgi?id=758864
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=744982
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This allows manually compiling dconf databases outside of /etc. This is meant
to be used from the build system of projects that want to install dconf
databases (like gdm) to easily build the database in-tree.
https://bugzilla.gnome.org/show_bug.cgi?id=672303
|
|
|
|
|
|
|
| |
Add some more padding to 'dconf help' output to accomodate coming
additions.
https://bugzilla.gnome.org/show_bug.cgi?id=672303
|
|
|
|
|
|
|
|
| |
Instead of just ignoring errors when trying to parse keyfiles in a .d
directory, fail the compile outright. 'dconf update' will print the
error and attempt to move on to the next .d directory in line.
https://bugzilla.gnome.org/show_bug.cgi?id=672303
|
|
|
|
|
| |
automake seems to prefer AM_CPPFLAGS these days (and warns about use of
INCLUDES as being an "old name").
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rewrite the dconf-service using gdbus-codegen and generally cleaning
things up a lot. The DConfWriter class can now be reasonably subclassed
to create more complex types of dconf databases (such as ones that
are stored in the local runtime dir and synced up with an NFS home
directory).
Keep a cache of the keys in the database (instead of re-reading it every
time we try to make a change).
Drop support for the old D-Bus interface (now that we are two stable
releases since it was used).
Modify the commandline tool for 'dconf blame' to call the new interface.
|
|
|
|
|
|
|
|
|
|
|
| |
Some short while ago the maintainers of bash-completion came to the
pretty reasonable conclusion that completion files are not configuration
data and therefore should be stored in /usr/share rather than /etc.
The /etc path was kept for backwards compatibility, but we should really
get with the new system.
https://bugzilla.gnome.org/show_bug.cgi?id=678536
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fix the vapi file to properly describe the changed signal (including the
possibility of NULL tag).
Change the dconf tool's implementation of the signal handler (and
simplify it due to the changed semantics of the signal).
Do the same for the editor.
|
|
|
|
| |
And fit the .gitignore over the same issue, as well.
|
|
|
|
|
|
|
| |
Disable C compiler warnings entirely while building Vala code.
Fix-up a couple of legitimate issues plus one false-positive
(in service.c).
|
|
|
|
|
|
|
|
|
|
| |
Clean up the Makefiles and make them as similar as possible.
Move CFLAGS to a common point of definition and stop using -I so much.
Replace the 'dbus stub' with libdconf-mock.a in tests/. Fill in some
stubs for future mock code for shm and gvdb (just to get things
compiling for now).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit represents a rather complete rethinking of DConfEngine.
- the different kinds of sources are now properly abstracted. This
will make landing NFS support substantially easier.
- there is now substantially more internal documentation
- DConfEngineMessage is gone and replaced with ordinary function calls
to be implemented by the D-Bus glue code
- the GDBus glue has been factored out and is now shared between the
client library and GSettings
- the "outstanding" queue logic from the GSettings backend is now in
the engine
- all changes now go through a single API that accepts a (new)
DConfChangeset object. Currently this only supports the current
operations (ie: setting and resetting). In the future this object
will also support the directory operations required by GSettingsList
and will be the basis for the new approach to implementing the
'delayed' GSettingsBackend (which will be the method by which those
two concepts can co-exist).
The (internal) API of the engine changed substantially. This caused the
following:
- the libdconf client library has been rewritten in C. Most of the
complicated aspects of it (that made it more convenience to use
Vala) are now gone.
- during the rewrite of libdconf, the DConfClient API changed a bit to
look more like a proper GObject. It now makes GIO-style use of
thread-default main contexts and uses GObject signals for
notifications (instead of hand-rolled callbacks).
- the GSettings backend has been substantially simplified (the
"outstanding" logic is gone). No externally-visible changes.
- the dbus-1 backend has taken a copy of the old engine code for now
until it can be ported to the new engine and sufficiently tested.
No externally-visible changes.
- the dconf commandline tool and dconf-editor required minor changes
to adjust to the DConfClient API changes
There is a substantial amount of cleaning up and finishing of work to be
done. There are many stubs remaining. There are likely still a large
number of bugs.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=673834
|
|
|
|
| |
This prevents trying to read editor swap files as if they were keyfiles.
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is expected that users may have the same key set multiple times if
they use separate files in an 'override' type of situation. In this
case the higher-numbered file wins and we should silently ignore the key
set in the lower-numbered file.
This silences the warning message that we previously issued in that
case.
https://bugzilla.gnome.org/show_bug.cgi?id=664288
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch is a substantial cleanup of the 'dconf update' command. The
biggest 'clean up' aspect is less dependence on catch-all 'throws'
clauses and better error messages for specific failures.
The cleanup also brings a new feature: keyfiles are now read in a
pre-defined order so that keys defined in higher-numbered files have
precedence over low-numbered files (ie: if the same key is in a file
'10_a' and '20_b' then '20_b' will "win"). This portion of the patch is
based on a patch from Josselin Mouette.
https://bugzilla.gnome.org/show_bug.cgi?id=670494
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=663547
|
|
|
|
|
|
| |
It is now possible to have arrays of nullable types and some places
where we had the equivalent non-null type are now considered to be
errors.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix a crash caused by attempting to dereference index -1 of a string.
This is very obviously a bug, but has only become a problem on OpenBSD
where the allocator will apparently hand out addresses at the very start
of a page with invalid memory immediately before.
Problem caught by Antoine Jacoutot.
https://bugzilla.gnome.org/show_bug.cgi?id=662271
|
|
|
|
| |
These changes are upstream by now.
|
|
|
|
|
|
|
|
| |
We were incorrectly checking for NULL as a return value from Dir.open()
when that function as bound as throwing an exception on error -- so
catch the exception instead.
https://bugzilla.gnome.org/show_bug.cgi?id=662158
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The dconf service can not presently be run at the system level and it
doesn't make sense to support locks on user-level databases. It also
became clear that most distributors and sysadmins would rather work
directly with text files anyway, so we supported that directly instead.
For this reason, 'set lock' support has never been properly implemented.
All the plumbing was added for it though, which means we have it
appearing on the API of the client library and documented in the help of
the commandline tool. This is misleading, since these functions do
nothing at all (and actually contain bugs anyway since their
do-nothingness was never actually tested).
For now, we rip out these functions. We can add them back later if we
decide to support this properly.
|
|
|
|
|
| |
These should be in the same format as the system database keyfiles and
fairly similar to the GSettings keyfile backend format.
|
|
|
|
| |
Fixup from last commit.
|
|
|
|
|
|
|
| |
The bash completion file is meant to be sourced and not executed
directly.
https://bugzilla.gnome.org/show_bug.cgi?id=651936
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- regenerate the file when the lock dir timestamp changes
- send the proper dbus message
- write an actual value for the lock in the GVDB
(otherwise the reader won't see it)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Make the dconf command-line tool slightly more friendly by adding a help
command and invoking that on an unknown command instead of aborting.
|