| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
If we fail to write the database file, try g_mkdir_with_parents() to
create the parent directory and try again.
https://bugzilla.gnome.org/show_bug.cgi?id=689136
|
|
|
|
|
|
|
|
|
|
|
|
| |
4fce559d81bdd3841cfe16fd3a3e6b8e6e9e60f2 changed from using GHashTable
to database-mode changesets for caching the state of the database in the
service but we missed a case of g_hash_table_unref being called.
Fix that now.
Problem reported and fix suggested by Philippe Coval.
https://bugzilla.gnome.org/show_bug.cgi?id=691013
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Was seeing crashes in the latest gnome-ostree on login.
https://bugzilla.gnome.org/show_bug.cgi?id=690316
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This makes gnome-shell search more pleasant and useful.
|
| |
|
|
|
|
|
|
| |
Also make sure the generated files get cleaned.
'make distcheck' fixing.
|
|
|
|
| |
Since we now have a hard dependency on the newer GLib anyway.
|
|
|
|
| |
For new g_variant_new_from_bytes() API.
|
|
|
|
| |
More NFS safety: never mmap() a gvdb on the service side.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Drop gvdb_table_new_from_data() and add gvdb_table_new_from_bytes().
Since the underlying backingstore of a GvdbTable is now always
refcounted, drop the refcounting on GvdbTable itself.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Factor the code for reading and writing DConfChangeset databases to the
gvdb file format out from dconf-writer.c.
This will allow those functions to be used by other backend
implementations that want to store things in gvdb format (like on NFS).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also, slightly change the rules about begin/change/commit/end.
It used to be theoretically possible to call:
begin(), change(), commit(), change(), end().
but that is no longer supported (and it was never used anyway). Now the
only valid thing to do after a commit() is end().
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Port the DConfWriter to use database-mode changesets to represent the
contents of the database.
This allows us to drop our own copy of the reset algorithm.
Also, fix a bug whereby we tried to acquire a list of items from a
NULL gvdb table (in the case where the database does not already exist).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a new mode for DConfChangeset to represent the entire contents of a
dconf database.
Also add a dconf_changeset_change() call to either merge changesets or
apply a changeset to a database-mode changeset.
Doing this allows us to have only one instance of the algorithm to deal
with resets (ie: when resetting '/a/' we must reset all keys starting
with '/a/').
|
| |
| |
| |
| |
| | |
This ensures that we don't do the gdbus-codegen twice when running in
make -j.
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=686270
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=686262
|
| |
| |
| |
| | |
Provide a link to the bug with a justification for the unusual code.
|
| |
| |
| |
| |
| | |
On OpenBSD, mapping descriptors PROT_WRITE without also specifying
PROT_READ triggers a segfault.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
Otherwise xinclude won't find them during out-of-tree builds.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1) For embedded systems, it makes no sense to include documentation
of this kind on each image. So we might as well not even build
it.
2) For people bootstrapping systems from source code, documentation
is the source of many cyclical build loops. Allowing it to
be disabled helps cut these loops.
3) The Docbook stylesheets are distributed as Zip files, and
the gnome-ostree builder only consumes git repositories.
https://bugzilla.gnome.org/show_bug.cgi?id=681385
|
| |
| |
| |
| |
| |
| | |
Leak introduced in facae6ffcd5b2935f9b708eecb1fd5aa7c8ddf86.
Tracked down by Fabien Tassin in
https://bugzilla.gnome.org/show_bug.cgi?id=686573
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The existing code had a /* XXX */ for properly dealing with the case of
the user requesting the default value. We should probably implement
this...
https://bugzilla.gnome.org/show_bug.cgi?id=685316
|
| |
| |
| |
| |
| |
| | |
It's really just a GQueue...
https://bugzilla.gnome.org/show_bug.cgi?id=685316
|
| | |
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=654812
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=677652
|