blob: 518a422afe99ddee3c8b57453ac8c47041b5aacd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
Changes in dconf 0.5.1
======================
- Adjust to GDBus API changes
- Send correct object path in Notify on WriteMany
- Use printf() and exit() instead of g_error() to avoid too many crash
reports for now
- Require gobject-introspection 0.9.5
- Require vala 0.9.5
- Make dconf-editor optional
- Drop libgee requirement for dconf-editor
- Tweak shared library installation to make ldconfig happy
- Bump .gir version to dconf-1.0
- Fix introspection build with recent gobject-introspection
- Minor bug fixes
Changes in dconf 0.5
=====================
- Include a dconf-editor
- drop libtool
- allow compiling without gobject-introspection
- autotools/build fixups
- repair some broken use of tags
- many updates for glib API changes
- fix a crasher in the service
- prefer 'automake-1.11' if it is in the path
- add support for layering (ie: for system defaults)
- add support for multiple writers in one service
- add a shared memory status region to indicate if the gvdb is stale
this prevents dconf from having to reopen the file each time
- support keyfile-maintained system settings (via 'dconf update')
- port client library and commandline tool to vala
- client library no longer has unimplemented calls
(except for write_many_async, due to bugs in valac)
- gtk-doc is now complete for the client library
- install our own vapi
- support 'reset' in the GSettingsBackend
Changes in dconf 0.4
=====================
- fix crashes when the dconf database doesn't yet exist
- add some incomplete gtk-doc
- use new GVDB (note: dconf file format has incompatibly changed)
- implement GSettings sync()
- use string tags instead of sequence numbers since it was impossible
to have universally unique sequence numbers
- theoretical support for sharing dconf databases between machines with
different byte orders
- fix bug where first write was not successful when auto-starting
service
- FreeBSD build fixes
- client API cleanups
- GObject introspection support
- enable automake silent rules by default for tarball builds
|
