| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
It seems like 1.13 is still a bit too cutting-edge for some (including
Debian wheezy and gnome-continuous).
Drop the dependency back to 1.11.2 and add back ACLOCAL_AMFLAGS (but
without ACLOCAL_FLAGS).
We can reevaluate after jessie is released.
|
| |
|
|
|
|
|
| |
ACLOCAL_PATH has replaced this for some time now.
Bump automake dependency to 1.11.2 (this is the first automake that
knows about ACLOCAL_PATH).
|
| |
|
|
|
| |
Running find without path is not allowed on FreeBSD.
https://bugzilla.gnome.org/show_bug.cgi?id=723998
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
A couple of things were preventing autoreconf from working properly on
our tarball releases. Fix those up:
- the m4/ directory (with intltool and gtk-doc m4) was not being disted
- our ./autogen.sh invoked automake with --foreign, suppressing
warnings about missing ChangeLog, etc. Move that flag into
configure.ac so that they are still suppressed when using autoreconf.
https://bugzilla.gnome.org/show_bug.cgi?id=663961
|
| |
|
|
|
|
|
|
|
| |
Add i18n support using intltool and glib-gettext (to avoid the
well-known issues with vanilla gettext).
This patch is heavily based on a patch by Gabor Kelemen.
https://bugzilla.gnome.org/show_bug.cgi?id=642217
|
| |
|
|
| |
We'll get an incomplete report in that case anyway...
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
There is no (apparent) way to trim branch or line coverage data from
lcov output based on expression matching against the source file. This
means that we get coverage results that tell us (for example) that we
failed to test lines like 'g_assert_not_reached ();' or didn't test all
branches of a g_assert().
Add a script to read the lcov output and remove line or branch coverage
data according to a list of symbols that are known to have incomplete
coverage when operating as expected.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the shm code from the engine and the service and put it in a
separate convenience library in shm/.
Remove the vestigial shmdir weirdness from the service (since shmdir is
now always relative to XDG_RUNTIME_DIR and has been for some time).
The purpose of this is so that dconf-engine can be properly unit-tested.
dconf-engine now has five points of contact with the world (excluding
the users of the engine themselves):
- the DCONF_PROFILE environment variable
- fopen() of profile files
- shm
- gvdb
- dbus
The environment variable is quite easily controlled. fopen() is
intercepted in the engine testcase with a interpose of the libc symbol.
With this commit now each of dbus, gvdb and shm are implemented in
separate utility modules that can be mocked from the testcases.
|
| |
|
|
|
|
|
|
|
| |
This will allow DConfClient to be included in testcases without pulling
in everything else (allowing us to mock in things like the dbus
backend).
Reorder the toplevel Makefile so that this library gets built before we
try to build tests/.
|
| |
|
|
|
|
| |
You need to ./configure with --enable-gcov and then type 'make lcov'.
HTML report goes into ./lcov-html/index.html
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
One -fPIC and one without.
This is done instead of pulling the various source files from other
Makefiles.
|
| |
|
|
|
| |
tests/ depends on libdconf-dbus-1 so build that first. Also make sure
the proper .so files are generated.
|
| | |
|
| | |
|
| |
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=622257
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Only very preliminary functionality for all of these.
|
| |
|
