summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* dconf 0.10.00.10.0dconf-0.10Ryan Lortie2011-09-262-1/+6
|
* dconf 0.9.10.9.1Ryan Lortie2011-09-191-0/+11
|
* Finish removing 'set_locked'Ryan Lortie2011-09-192-18/+0
| | | | A few leftovers from the tear-out: docs and header file.
* fix dconf_shmdir_from_environmentMarc-Antoine Perennou2011-09-121-1/+1
| | | | | | Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com> https://bugzilla.gnome.org/show_bug.cgi?id=658864
* Merge remote-tracking branch 'gvdb/master'Ryan Lortie2011-09-122-2/+4
|\
| * hashing: always use signed charsRyan Lortie2011-09-122-2/+2
| | | | | | | | | | | | | | | | | | | | Our hashing of non-ASCII strings was undefined due to the fact that 'char' is signed on some platforms, unsigned on others. Always use a signed char. Discovered by Alexander Larsson. https://bugzilla.gnome.org/show_bug.cgi?id=658806
| * builder: do not include <unistd.h> on win32Ryan Lortie2011-04-151-0/+2
| | | | | | | | | | | | Spotted by Kean Johnston <kean.johnston@gmail.com>. https://mail.gnome.org/archives/gtk-devel-list/2011-April/msg00010.html
* | Remove "service func" logicRyan Lortie2011-09-117-104/+4
| | | | | | | | | | | | This was required to support the case where the dconf client was unable to determine the cache directory for itself. Since we now use the XDG runtime directory, this is redundant.
* | Graceful exit on signalRyan Lortie2011-09-112-1/+17
| | | | | | | | | | | | Exit gracefully on receipt of SIGTERM, SIGHUP or SIGINT. Require glib 2.29.90 for the API used to do this.
* | Add \n to error messageRyan Lortie2011-09-111-1/+1
| |
* | Remove 'set lock' support from dconfRyan Lortie2011-09-119-130/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | GSettings: g_warning() on failure to communicateRyan Lortie2011-08-151-5/+32
| | | | | | | | | | | | | | When we have a failure to deliver requests to the dconf backend, give a g_warning(). https://bugzilla.gnome.org/show_bug.cgi?id=641768
* | dconf: increase minimum glib versionRobert Schwebel2011-07-271-1/+1
| | | | | | | | | | | | | | | | | | | | G_DBUS_SIGNAL_FLAGS_NO_MATCH_RULE was introduced only in glib-2.27.3, so this is the minimum required glib version now. 34b297bd6ab4110978709d7cf49b60d7aa1ea90d changes the minimal version to 2.27.2, but the symbol was really only introduced in 2.27.3. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* | bump versionRyan Lortie2011-07-261-1/+1
| |
* | dconf 0.9.00.9.0Ryan Lortie2011-07-262-1/+47
| |
* | gitignore stuffRyan Lortie2011-07-261-0/+1
| |
* | Don't hide dconf-editorRyan Lortie2011-07-261-1/+0
| | | | | | | | | | Let dconf-editor show in the applications list. If someone installed it then it is appropriate for them to see it.
* | Remove unused 'error' variableRyan Lortie2011-07-241-3/+2
| | | | | | | | | | | | | | | | | | We never consumed the value, and then we reused it, causing warnings about uninitialised error variables. Just remove it altogether. Caught by Matthias. https://bugzilla.gnome.org/show_bug.cgi?id=655193
* | Support maybe types in dconfRyan Lortie2011-07-222-5/+77
| | | | | | | | | | | | | | | | | | Work around the fact that we can't send maybe types over D-Bus by sending a blob of serialised GVariant data instead. Abuse the fact that we're using an array to denote 'maybe' at the level of the dconf protocol and fill that array with 2 items (which would not otherwise be possible) to indicate this special case.
* | cli: add keyfile-based "dump" and "load" commandsRyan Lortie2011-07-214-4/+110
| | | | | | | | | | These should be in the same format as the system database keyfiles and fairly similar to the GSettings keyfile backend format.
* | Remember to dist the completion file.Ryan Lortie2011-07-051-1/+1
| | | | | | | | Fixup from last commit.
* | Don't install bash completion file as executable scriptMichael Biebl2011-07-031-1/+1
| | | | | | | | | | | | | | The bash completion file is meant to be sourced and not executed directly. https://bugzilla.gnome.org/show_bug.cgi?id=651936
* | Simplify 'shmdir' checksRyan Lortie2011-07-031-44/+7
| | | | | | | | | | | | With XDG_RUNTIME_DIR, we no longer have to be frightened about NFS. That lets us remove the NFS checks that were causing build failures all over the place.
* | Deal with incompatible changes in ValaRyan Lortie2011-07-031-0/+12
| | | | | | | | | | | | | | | | | | | | Vala 0.13 (leading toward 0.14) corrects an error in the binding for GtkTreeModel. Unfortunately, the correction is incompatible and there is no way to have code that will work with both old and new Vala compilers. Rather than hard-depend on the unstable Vala release, just use two separate declarations decided on #if VALA_0_14.
* | Add change watching to dconf-editorRyan Lortie2011-06-221-1/+22
| | | | | | | | | | | | | | Watch for changes to DConf and update the view. This is not done in the most elegant or efficient way, but it's simple and it works. https://bugzilla.gnome.org/show_bug.cgi?id=649443
* | cli: make 'dconf watch' actually write outputRyan Lortie2011-05-101-1/+24
| |
* | Properly support watching in DConfClientRyan Lortie2011-05-101-0/+30
| |
* | Don't compare VariantType by pointer valueRyan Lortie2011-05-101-1/+1
| |
* | Add 'dconf reset'.Ryan Lortie2011-05-092-3/+39
| |
* | Fix copyright lineRyan Lortie2011-05-091-2/+2
| |
* | Handle flagsRobert Ancell2011-05-092-11/+68
| | | | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=645611
* | post-release bumpRyan Lortie2011-05-091-1/+1
| |
* | 0.7.5 release0.7.5Ryan Lortie2011-05-092-1/+14
| |
* | editor: Load schemas from GSETTINGS_SCHEMA_DIR if setRui Matos2011-05-091-1/+10
| | | | | | | | Fixes https://bugzilla.gnome.org/show_bug.cgi?id=622292
* | editor: Don't crash on empty schema descriptionsMatthias Clasen2011-05-091-2/+2
| | | | | | | | Based on a patch from Fabian Deutsch <fabian.deutsch@gmx.de>
* | editor: Change default sizeRobert Ancell2011-05-081-2/+2
| |
* | editor: Fix gsettings pathRobert Ancell2011-05-081-1/+1
| |
* | editor: Set shadow type for on scrolled windows to "in"Jean-François Fortin Tam2011-05-081-0/+2
| | | | | | | | Fixes https://bugzilla.gnome.org/show_bug.cgi?id=641293
* | editor: Remember window sizeRobert Ancell2011-05-085-2/+62
| | | | | | | | Fixes https://bugzilla.gnome.org/show_bug.cgi?id=641293
* | Fix crash when user database is not presentRyan Lortie2011-05-081-1/+5
| | | | | | | | | | | | | | If we fail to open the database in the user's home directory then the variable will be NULL. The refactor of the read function for lockdown support missed this check, resulting in a rather dramatic crash on fresh accounts.
* | update the NEWSRyan Lortie2011-05-061-0/+21
| |
* | dist .tar.xzRyan Lortie2011-05-061-1/+1
| |
* | bump versionRyan Lortie2011-05-061-1/+1
| |
* | Optimise is_writable() for the common caseRyan Lortie2011-05-061-14/+17
| | | | | | | | ...of no system defaults database.
* | Remove accidental debugging spewRyan Lortie2011-05-061-2/+0
| |
* | client-side lockdown supportRyan Lortie2011-05-063-36/+114
| | | | | | | | | | | | | | | | | | Support lockdown on the client side for GSettings. For performance reasons only lockdown of specific keys (not entire subpaths) is supported at the moment. This may change in the future if we can find a way to make large numbers of related GVDB lookups sufficiently performant.
* | dconf update: more lockdown fixesRyan Lortie2011-05-061-3/+9
| | | | | | | | | | | | | | | | | | - 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)
* | dconf update: support lockdownRyan Lortie2011-05-051-0/+39
| |
* | Change locking in the engineRyan Lortie2011-05-051-7/+28
| | | | | | | | | | | | | | | | | | | | Switch from code locking to data locking and hold the data lock quite a lot more often. We could try to be more clever about finding ways to hold locks less often but I think it's not really worth it. Closes #648949
* | dconf update: don't attempt to open non-filesRyan Lortie2011-05-051-0/+6
| |
View Lorry Controller Status