summaryrefslogtreecommitdiff
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* Namespace the dependencies variablesEmmanuele Bassi2018-08-111-2/+2
| | | | | | | | | | | | | The build currently, unintentionally, depends on side effects, namely: that a variable defined in a meson.build file will be valid for any other included meson.build file, until it gets re-defined. We use the same `deps` variable in many places, and we end up depending on the inclusion order when we get to the client library, which depends on the gsettings backend defining the `deps` variable. Reviewed-by: nobody Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* build: Add trailing commas where necessaryIñigo Martínez2018-08-111-4/+4
| | | | | | Having trailing commas in place means that if another source file or parameter is added to the end of the list or function, there won't be noise when adding the comma to the line above.
* build: Do not make heavy use of project_nameIñigo Martínez2018-08-111-1/+1
| | | | | | | | | The current meson build files make heavy use of meson's `project_name` function. However this makes difficult for any developer to find for given program/library/file names. The project name is also never going to change. Due to this reason these calls have been changed for `dconf` itself.
* build: Use completions dir from pkg-config fileIñigo Martínez2018-08-111-4/+6
| | | | | | | | | | | | The `bash-completions` pkg-config file provides a variable with the location of the completion files. This variable is checked to set the installation directory of the completion file provided by dconf. As a side note, the variable in the `bash-completions` pkg-config file is not totally correct, because it provides a directory that is relative to prefix while it should be relative to datadir.
* build: Remove duplicated warning parameterIñigo Martínez2018-08-111-1/+0
| | | | | | | The `dconf` binary uses the `-w` compiler argument which is already added by meson by default. This duplicated parameter has been removed.
* build: Remove unnecessary variablesIñigo Martínez2018-08-111-2/+1
| | | | | | | | | There are some defined variables that are not used. Some of these variables are also used as install directories, that are equal to default installation directories. These all unnecessary variables and default installation directories have been removed.
* build: Fix internal dependenciesIñigo Martínez2018-08-111-0/+1
| | | | | | | | | meson is able to generate internal dependencies for handling built libraries. These internal dependencies depend on other dependencies as well, based on the includes exposed by their headers. This have been fixed by using proper internal dependencies for these libraries.
* bin: Stop copying a delegatePhilip Withnall2018-08-101-1/+1
| | | | | | | | | This fixes a build warning: ../bin/dconf.vala:310.15-310.18: warning: copying delegates is not supported ../bin/dconf.vala:305.2-305.13: warning: copying delegates is not supported Signed-off-by: Philip Withnall <withnall@endlessm.com>
* dconf: fix command line completion for "dconf update"Andrea Stacchiotti2018-08-081-2/+2
| | | | | | | Due to a typo, there was no "update" completion option, but a " update" one, which required the user to type "\ " to get a completion, instead of "u". https://bugzilla.gnome.org/show_bug.cgi?id=758126
* dconf-update.vala: correct error message grammarKenyon Ralph2018-07-261-1/+1
|
* Remove .gitignore filesIñigo Martínez2017-10-221-3/+0
| | | | | | | | | | 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
* build: Remove autotoolsIñigo Martínez2017-10-171-26/+0
| | | | | | | To avoid the burden of maintaining multiple build systems, this patch removes autotools support. https://bugzilla.gnome.org/show_bug.cgi?id=784910
* build: Port to meson build systemIñigo Martínez2017-10-172-1/+27
| | | | | | | | 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
* client: replace _read_default() with _read_full()Allison Ryan Lortie2015-12-161-9/+3
| | | | | | | | | 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
* dconf(1): add -d option to 'dconf read'Allison Ryan Lortie2015-11-301-4/+18
| | | | | | Add a -d option to 'dconf read' to read the default value. https://bugzilla.gnome.org/show_bug.cgi?id=758864
* dconf(1) tool: add list-locks commandAllison Ryan Lortie2015-11-301-12/+29
| | | | | | | 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
* dconf(1): fix whitespace in synopsisAndreas Schwab2015-03-021-3/+3
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=744982
* dconf compile: always write little endianRyan Lortie2014-02-051-1/+4
|
* Updated FSF's addressDaniel Mustieles2014-01-312-6/+2
|
* dconf(1): add 'dconf compile' commandRyan Lortie2014-01-132-0/+29
| | | | | | | | 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
* dconf(1): some whitespace changesRyan Lortie2014-01-131-16/+16
| | | | | | | Add some more padding to 'dconf help' output to accomodate coming additions. https://bugzilla.gnome.org/show_bug.cgi?id=672303
* dconf update: change error handlingRyan Lortie2014-01-131-52/+44
| | | | | | | | 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
* don't use INCLUDESRyan Lortie2013-07-121-1/+1
| | | | | automake seems to prefer AM_CPPFLAGS these days (and warns about use of INCLUDES as being an "old name").
* service: rewriteRyan Lortie2012-10-231-1/+1
| | | | | | | | | | | | | | | | 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.
* Install dconf CLI bash completion in /usr/shareRyan Lortie2012-07-152-2/+2
| | | | | | | | | | | 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
* Fixup srcdir != builddir fallout from last commitRyan Lortie2012-07-151-1/+1
|
* Fix up the "changed" signal for ValaRyan Lortie2012-07-101-13/+8
| | | | | | | | | | 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.
* Update the editor and cli to use the new sonameRyan Lortie2012-07-101-1/+1
| | | | And fit the .gitignore over the same issue, as well.
* clean up C compiler warningsRyan Lortie2012-07-081-1/+3
| | | | | | | Disable C compiler warnings entirely while building Vala code. Fix-up a couple of legitimate issues plus one false-positive (in service.c).
* massive Makefile reorganisationRyan Lortie2012-07-082-6/+15
| | | | | | | | | | 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).
* add gtester supportRyan Lortie2012-07-061-0/+2
|
* Massively reorganise the client-sideRyan Lortie2012-07-023-37/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* dconf cli: call setlocale() on startupRyan Lortie2012-04-101-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=673834
* dconf update: ignore dotfilesRyan Lortie2012-03-191-0/+4
| | | | This prevents trying to read editor swap files as if they were keyfiles.
* dconf update: don't warn on a key set twiceRyan Lortie2012-03-191-2/+4
| | | | | | | | | | | | 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
* dconf update: Read keyfiles in a defined orderRyan Lortie2012-03-192-78/+95
| | | | | | | | | | | | | | 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
* cli: add undocumented 'dconf blame' optionRyan Lortie2012-03-071-0/+8
|
* cli: Fix help message to include 'load' and 'dump'Roberto C. Morano2012-02-061-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=663547
* adjust to recent changes in vala compilerRyan Lortie2011-12-281-2/+2
| | | | | | 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.
* Silence some harmless warnings from vala codeRyan Lortie2011-11-211-1/+1
|
* dconf update: don't access before start of stringRyan Lortie2011-11-011-1/+3
| | | | | | | | | | | | 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
* drop fixes.vapiRyan Lortie2011-10-193-6/+2
| | | | These changes are upstream by now.
* Fix error handling for missing *.d/locks/ dirRyan Lortie2011-10-191-2/+4
| | | | | | | | 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
* Remove 'set lock' support from dconfRyan Lortie2011-09-111-32/+0
| | | | | | | | | | | | | | | | | | 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.
* 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
* cli: make 'dconf watch' actually write outputRyan Lortie2011-05-101-1/+24
|
* Add 'dconf reset'.Ryan Lortie2011-05-092-3/+39
|
* Fix copyright lineRyan Lortie2011-05-091-2/+2
|
View Lorry Controller Status