@markus2330 markus2330 released this Aug 18, 2018 · 633 commits to master since this release

Assets 3

0.8.24 Release

We are proud to release Elektra 0.8.24.

  • guid: 889b700d-9eac-4eff-9a3d-f6fb15c3d9da
  • author: Markus Raab
  • pubDate: Sat, 18 Aug 2018 18:13:40 +0200
  • shortDesc: Elektra Web, Notifications, Type System

What is Elektra?

Elektra serves as a universal and secure framework to access
configuration settings in a global, hierarchical key database.
For more information, visit https://libelektra.org.

For a small demo see here:


You can also read the news on our website


  • Elektra Web
  • Notifications
  • KDE Workshop
  • Type System Prototype
  • Chef Cookbook

Elektra Web 1.6

The new release of Elektra Web features many UX improvements from the usability test!

Elektra Web 1.6 video

Try it out now on: http://webdemo.libelektra.org/

1.5 changelog:

  • search completely reworked - it does not act as a filter on already opened keys anymore, and instead searches the whole key database - feedback from the search was also greatly improved (pulsating while searching, glowing blue when done)
  • added "abort" buttons to dialogs to revert actions
  • added "create array" button to easily create arrays
  • removed confirmation dialog before deletion (undo can be used instead)
  • created a docker image: elektra/web
  • implemented auto-deployment of webdemo.libelektra.org
  • small fixes:
    • updated visibility levels
    • removed "done" button in main view
    • fixed issues with the opener click area
    • remove metakeys when they are set to the default value or empty/0
    • improved keyboard support
    • fixed many small issues (#2037)

1.6 changelog:

  • fixed bugs related to arrays (#2103)
  • improved performance of search for many results
  • added 404 page for invalid instance ids
  • implement drag & copy by holding the Ctrl or Alt key
  • add button to show error details
  • allow deleting all keys in a namespace

Thanks to Daniel Bugl.


Elektra's notification feature which allows applications to keep persistent
configuration settings in sync with the key database and other applications was
greatly improved with this release:

More details can be found in this news.
Check out the updated notification tutorial
and notification examples (polling,
async and

KDE Workshop

At Akademy 2018 we had a successful
Config Workshop.

We generally agreed that misconfiguration is important and the situation
in FLOSS needs to improve.
We discussed how Elektra can be used in KDE and came up with the idea that
KConfig could be moved to a Elektra plugin.
Then KConfig could be patched to use Elektra instead.
This would lead to the situation that KDE users would have the same user
experience with the advantages of Elektra, like:

  • Elektra Web and qt-gui to safely modify all settings
  • modification of settings via configuration management tools
  • switch to other configuration file formats (e.g., XML or YAML for plasma)
  • provide notification with main-loop integration
  • plugin system for LDAP support and similar features

For more information see the Slides

Type System Prototype

Elektra supports specifying the semantics of keys via metakeys in the spec
namespace. An example is the metakey check/range which can be used to specify
that a key only holds numbers in a given range. Another metakey is check/enum
which only allows specific keywords to be the content of a key. Up to now these
semantics are only being checked at runtime. Therefore a type system was developed to
be able to check configuration specifications statically. As an example, it
would detect when one accidentally adds both a range and an enum check if their
possible contents are not compatible with each other.

The type system is available as a plugin that gets mounted along with a
configuration specification into the spec namespace. Furthermore we include a
set of type definitions for commonly used metakeys such as check/range,
check/enum, check/validation, fallback or override.

For more details see the
typechecker readme

Thanks to Armin Wurzinger.

Chef Cookbook

Next to the Puppet Resource Type
we now also prepared a Chef Cookbook
which allows us to use Elektra from within Chef.

For example, to set mount a configuration file, you can use:

kdbmount 'system/hosts' do
	file '/etc/hosts'
	plugins 'hosts'
	action :create

And to add an hosts entry, you can use:

kdbset '/hosts/ipv4/showthatitworks' do
	namespace 'system'
	value ''
	action :create

Note that currently kdb is invoked
and Elektra needs to be installed for
managed systems.

Thanks to Michael Zronek and Vanessa Kos.



  • We fixed various warnings in the source code reported by OCLint. (René Schwaiger)
  • The plugin now also encodes and decodes key names in addition to key values. (René Schwaiger)

CPP Template

  • We added a new template for C++ based plugins. To create a plugin based on this
    template, please use the command

    scripts/copy-template -p pluginname

    , where pluginname specifies the name of your new plugin. (René Schwaiger)


  • The crypto plugin now uses Elektra's libinvoke and the base64 plugin in order to encode and decode Base64 strings. This improvement reduces code duplication between the two plugins. (Peter Nirschl)


  • Changed behaviour of export to validate the structure of exported keys only. (Thomas Waser)

Directory Value

  • We rewrote the plugin using C++. (René Schwaiger)
  • Directory Value now also supports nested arrays. (René Schwaiger)
  • The plugin now also adds leafs for a key, if its value is null or the empty string. (René Schwaiger)


  • The fcrypt plugin will consider the environment variable TMPDIR in order to detect its temporary directory. See [#1973] (Peter Nirschl)


  • The fstab plugin now passes tests on musl builds. (Lukas Winkler)


  • An issue when building Haskell plugins with a cached sandbox is fixed in case
    a Haskell library bundled with Elektra gets changed. (Armin Wurzinger)
  • The script that generates the list of haskell dependencies now also works on
    ghc8.0.1 and older cabal versions. Furthermore one can specify the build directory as
    a parameter if it is not located within the source directory. (Armin Wurzinger)

Interpreter Plugins

  • The plugins Ruby, Python and Jni can now also be mounted as global plugin.
  • Fix crashes in global Python plugin by using pluginprocess.
    Python plugin can now shutdown properly again. (Markus Raab and Armin Wurzinger)


  • We now disable the plugin for the BUILD_STATIC or BUILD_FULL build variants, since otherwise the plugin breaks the kdb tool.
    (René Schwaiger)
  • We disabled the internal check (testscr_check_kdb_internal_check) for the plugin, since it always fails. (René Schwaiger)


  • The plugin hexnumber has been added. It can be used
    to convert hexadecimal values into decimal when read, and back to hexadecimal when written. (Klemens Böswirth)


  • The list plugin now allows us to pass
    common configuration for all plugins by using keys below the "config/" setting.
    The updated plugin documentation contains more information and an example. (Thomas Wahringer)
  • The list plugin which is responsible
    for global mounting had a bug which prevented globally mounted plugins from
    being configurable. (Thomas Wahringer)


  • We fixed a memory leak in the mINI plugin by requiring the plugin
    ccode instead of the “provider” code. (René Schwaiger)
  • Removed unused header files. (René Schwaiger)


  • Fixed an error in network plugin that prevented it from working on non-glibc
    platforms. (Lukas Winkler)


Regex Dispatcher

  • The plugin regexdispatcher has been added.
    It calculates regex representations for commonly used specification keywords to be used with the
    typechecker. Currently the keywords check/range,
    check/enum and default are supported. (Armin Wurzinger)


  • The plugin typechecker, used to validate
    configuration specifications for Elektra statically, has been improved under the hood. It now
    supports a more concise and efficient typechecking process including a greatly
    improved type inference scheme that should make generated specification files and thus
    generated errors to be easier to understand. An example of such error message is shown in the
    README. (Armin Wurzinger)


  • The tcl plugin does not fail anymore, if its configuration file does not exist and you try to
    retrieve the plugin contract. (René Schwaiger)
  • The plugin now uses relative key names. This update addresses issue #51. (René Schwaiger)


  • The YAJL Plugin now uses the internal logger functionality instead of printf statements.
    (René Schwaiger)
  • We fixed a problem with negative values reported by the
    UndefinedBehaviorSanitizer. (René Schwaiger)


  • The plugin does not save empty intermediate keys anymore. The example below shows the old and the new behavior of the plugin:

    # Mount plugin
    kdb mount config.yaml /tests/yamlcpp yamlcpp
    # Store single key-value pair
    kdb set /tests/yamlcpp/level1/level2/level3 value
    # Old behavior
    kdb ls /tests/yamlcpp
    #> user/tests/yamlcpp/level1
    #> user/tests/yamlcpp/level1/level2
    #> user/tests/yamlcpp/level1/level2/level3
    # New behavior
    kdb ls /tests/yamlcpp
    #> user/tests/yamlcpp/level1/level2/level3

    . (René Schwaiger)

  • YAML CPP now requires at least yaml-cpp 0.6, since the current
    MSR test for the plugin triggers two bugs:

    in earlier versions of the yaml-cpp library. (René Schwaiger)

  • The plugin does now support arrays containing empty fields. (René Schwaiger)

  • YAML CPP now also adds array meta data for arrays containing arrays. (René Schwaiger)

  • The plugin now also supports empty arrays:

    kdb mount test.yaml user/tests/yamlcpp yamlcpp
    kdb setmeta user/tests/yamlcpp/array array ''
    kdb export user/tests/yamlcpp/array yamlcpp
    #> []


  • YAML CPP now handles null values containing meta data properly:

    kdb mount test.yaml user/tests/yamlcpp yamlcpp
    kdb set user/tests/yamlcpp/null
    kdb setmeta user/tests/yamlcpp/null comment 'Null Key'
    kdb export user/tests/yamlcpp/null yamlcpp
    #> !<!elektra/meta>
    #> - ~
    #> - comment: Null Key


YAML Smith

  • YAML Smith is a plugin that converts Elektra’s KeySet data structure to a textual
    representation in the YAML serialization format. The plugin is currently in a very early stage of development. Please be advised,
    that it is quite likely that the plugin will produce incorrect or even invalid YAML data, especially if your KeySet contains special

Yan LR

  • The experimental Yan LR plugin uses a parser, generated by ANTLR to read
    basic YAML data. The plugin only converts YAML data to Elektra’s KeySet data structure. If you want to write data in the YAML
    format please take a look at the YAML Smith plugin. (René Schwaiger)

ZeroMQ transport plugins

  • New notification transport plugins for ZeroMQ were added.
    The new "zeromqsend" and "zeromqrecv" plugins use
    ZMQ_PUB and ZMQ_SUB sockets to send and receive notifications.
    The plugins can be used instead or along with the
    "dbus" and
    "dbusrecv" transport plugins.
    Check out the
    plugin documentation for more
    information. (Thomas Wahringer)




  • Replaced strdup with elektraStrDup (for C99 compatibility). (Markus Raab)
  • You can now remove the basename of a key via the C++ API by calling key.delBaseName(). (René Schwaiger)
  • The function elektraArrayGetNextKey now uses NULL instead of the empty string as init value for the returned key. (René Schwaiger)


  • The library pluginprocess that is used to
    execute plugins run inside own processes has been improved. This is useful as some plugins like
    haskell-based plugins or python can only be started once
    inside a single process, while libelektra may call a plugin several times. The library now uses an
    improved communication protocol that separates between pluginprocess-related data and keysets
    passed to plugins. This avoids any possible name clashes between keys used by a plugin and keys
    used by pluginprocess.
    The documentation of the plugin has been improved as well, some mistakes were corrected and it
    should be more clear how to store plugin data besides pluginprocess's data structure.
    Tests have been added to the library to ensure its correct functionality. (Armin Wurzinger)
  • Anonymous pipes are now used instead of named pipes for the communication as anonymous pipes get
    terminated by the OS in case a child process dies before writing back data to the parent.
    Currently the parent process will freeze otherwise attempting to read from the child. (Armin Wurzinger)


  • A new I/O binding for ev has been
    It can be used to integrate the notification feature with applications based
    on ev main loops. (Thomas Wahringer)


  • The
    notification API
    was extended.
    The API now supports more types: int, unsigned int,
    long, unsigned long, long long, unsinged long long, float and double.
    It also supports all of Elektra's kdb_*_t types defined in kdbtypes.h.
    Also contexts for callbacks were added and
    elektraNotificationRegisterCallbackSameOrBelow() allows for notifications
    for the registered key or below. (Thomas Wahringer)


  • The new tool kdb find lists keys of the database matching a certain regular expression. (Markus Raab)
  • You can now build the Qt-GUI using Qt 5.11. (René Schwaiger)


  • The script check_formatting.sh now also checks the formatting of CMake
    code if you installed sponge and cmake-format. (René Schwaiger)
  • The script check_formatting.sh now no longer writes to stdout if clang-format5.0
    can not be found. (Lukas Winkler)
  • The script check_bashisms.sh should now work correctly again, if the
    system uses the GNU version find. (René Schwaiger)
  • The script reformat-cmake now checks if cmake-format works before it reformats CMake files. Thank you to Klemens Böswirth for the detailed description of the problem. (René Schwaiger)
  • scripts/run_icheck now no longer leaves the base directory of the project
    when checking if the ABI changed. (Lukas Winkler)
  • The completion for fish now also suggest the info/ meta attributes of the
    file plugin. (René Schwaiger)

Copy Template

  • The script copy-template is now location independent. It will always create a
    new plugin in src/plugins. (René Schwaiger)
  • The command now also supports the new template for C++ based plugins. Please use the
    command line switch -p to create a new plugin based on cpptemplate.


  • We improved the formatting of our compilation guide. (René Schwaiger)
  • We fixed various minor spelling mistakes in the documentation. (René Schwaiger)
  • The man pages for kdb change-resolver-symlink and
    kdb change-storage-symlink referenced the wrong command.
    (Lukas Winkler, René Schwaiger)
  • We added documentation for our build system in
    (Lukas Winkler)
  • The documentation for kdb and kdb set now mentions the -- argument that stops processing of command line switches. This is useful
    for setting negative values among other things. (Klemens Böswirth)
  • We added a new tutorial about the jna binding. The tutorial shows how to use the java library to interact with kdb (Michael Zronek)
  • GitHub now detects the license of the repository correctly again. (René Schwaiger)
  • We added a tutorial describing Elektra’s array data type. (René Schwaiger)


(Markdown) Shell Recorder

  • We added new Markdown Shell Recorder tests for the
  • (Markdown) Shell Recorder tests now save test data below /tests (see issue #1887). (René Schwaiger)
  • The Markdown Shell Recorder checks kdb set commands to ensure we only add tests that store data below /tests. (René Schwaiger)
  • The Markdown Shell Recorder now supports indented code blocks. (René Schwaiger)
  • The Markdown Shell Recorder now also tests if a command prints nothing to stdout if you add the check #>. (René Schwaiger)
  • We fixed some problems in the Markdown Shell Recorder test
    of kdb ls. (René Schwaiger)
  • The Shell Recorder now does not interpret - in checks as option character any more. (René Schwaiger)
  • The add_plugin helper now respects ENABLE_KDB_TESTING when adding
    Markdown Shell Recorder tests. (Lukas Winkler)
  • The Markdown Shell Recorder test for kdb find now removes the configuration file
    at the end of the test. (René Schwaiger)
  • The Shell Recorder now properly unmounts any additional mountpoints created
    during a test. (René Schwaiger)
  • We removed the broken auto unmounting feature from the Markdown Shell Recorder. (René Schwaiger)
  • The Markdown Shell Recorder does not require a bash compatible shell anymore. (René Schwaiger)


  • Plugins added with the flag SHARED_ONLY no longer get tested in the script check_kdb_internal_check.sh if executed with kdb-full or kdb-static. (Armin Wurzinger)
  • Add compare_regex_to_line_files which allows to compare a file made of
    regex patterns to be compared with a text file line by line.
    (Lukas Winkler)
  • The OPMPHM has a new test case (Kurt Micheli)
  • Do not execute fcrypt and crypto unit tests if the gpg binary is not available. (Peter Nirschl)
  • Resolved an issue where tests did not cleanup properly after they ran.
    This was especially noticeable for gpg tests as the gpg-agents that were
    spawned did not get cleaned up afterwards. (Lukas Winkler)
  • We disabled the general plugin test (testkdb_allplugins) for the semlock plugin, since the
    test reported memory leaks on the latest version of Debian Unstable. (René Schwaiger)
  • The CFramework macro compare_keyset now supports the comparison of two empty key sets. (René Schwaiger)
  • The C++ version of the macro exit_if_fail now really exits the test progamm if the test fails. (René Schwaiger)
  • The C++ testing framework now supports the macro compare_keyset that checks if two key sets are equal. (René Schwaiger)


As written in the previous release notes:

  • Debian Wheezy is not supported anymore.
  • Jessie (oldstable) with gcc 4.8.4 is now the oldest supported platform.

Another important change is:

  • We now import the current version of Google Test as external project at configuration time using
    DownloadProject. If you want to use a local installation of
    Google Test instead, please set the value of GTEST_ROOT to the path of you local copy of the
    Google Test framework. (René Schwaiger)
  • The cmake variable GTEST_ROOT now respects the environment variable
    GTEST_ROOT if it is set. (Lukas Winkler)


  • The build system no longer installs Haskell dependencies from hackage by itself, instead
    this has to be done beforehand like it is the case with all other dependencies. The main
    reason is that the build servers shouldn't compile the dependencies over and over again,
    only if something changes. See the README. (Armin Wurzinger)

  • Plugins can be specified to be only built for BUILD_SHARED builds, but to be excluded
    from any BUILD_FULL or BUILD_STATIC builds using the new optional argument ONLY_SHARED
    for our cmake macro add_plugin. This way BUILD_SHARED can be combined with the other
    options without excluding such plugins. The cmake messages about plugin inclusion have
    been updated to indicate this behavior. This behavior has been applied for the Haskell
    plugins- and bindings and JNI plugin as they currently don't support full or static builds.
    (Armin Wurzinger)

  • The build system does not install Google Test anymore if you install Elektra. (René Schwaiger)

  • We disabled the test testlib_notification on ASAN enabled builds, since Clang reports that the test leaks memory. (René Schwaiger)

  • Disable Markdown Shell Recorder test validation.md for ASAN builds.
    It leaks memory and thus fails the test during spec mount. (Lukas Winkler)

  • Haskell plugins and bindings are now correctly excluded when using BUILD_FULL or BUILD_STATIC
    as this is currently unsupported. Another issue when building Haskell plugins with a cached sandbox
    is fixed as well. (Armin Wurzinger)

  • Fix compilation with BUILD_TESTING=OFF when spec or list plugins are not selected.

  • Set coverage prefix to PROJECT_SOURCE_DIR, resulting in easier readable
    coverage reports. (Lukas Winkler)

  • The functions add_plugintest and add_plugin now also support adding a C++ test instead of a C test. (René Schwaiger)

  • The function add_plugintest now also supports setting environment variables for C/C++ based tests. (René Schwaiger)

  • The build system now automatically detects Homebrew’s OpenSSL version on macOS. (René Schwaiger)

  • We improved the automatic detection of Libgcrypt and OpenSSL. (René Schwaiger)

  • Resolved an issue where cmake did not properly set test feature macros to detect and use libc functionality. (Lukas Winkler)

  • Improve the detection of ftw.h, if the current build use the compiler switch -Werror. (René Schwaiger)

  • We now ignore warnings about

    • zero size arrays (Clang),
    • variadic macros (Clang, GCC),
    • conversions to non-pointer type (GCC), and
    • attribute warnings (GCC),

    caused by code generated via SWIG in the Ruby binding and plugin. (René Schwaiger)


  • clang-5.0 is now used for clang tests by the build system (Lukas Winkler)
  • An additional build job on Ubuntu:xenial has been added (Lukas Winkler)
  • withDockerEnv Jenkinsfile helper now no longer provides stages automatically. (Lukas Winkler)
  • Google Test is installed in Docker images used by the build system. (Lukas Winkler)



  • A build job checks if PRs modify the release notes. (Markus Raab)
  • Several improvements to the build system have been implemented (Lukas Winkler):
    • Better Docker image handling.
    • Abort of previously queued but unfinished runs on new commits.
    • Document how to locally replicate the Docker environment used for tests.
  • The Jenkins build server now also compiles and tests Elektra with enabled address sanitizer. (Lukas Winkler)
  • Add STATIC and FULL linked builds. (Lukas Winkler)
  • Ported GCC ASAN build job to new build system (René Schwaiger + Lukas Winkler)
  • Docker artifacts are now cleaned up in our daily build job. (Lukas Winkler)
  • clang tests have been ported to the new build system (Lukas Winkler et al)
  • icheck build server job has been ported to our new build system. (Lukas Winkler)
  • Port elektra-gcc-configure-debian-optimizations to new build system. (Lukas Winkler)
  • Port elektra-gcc-configure-mingw-w64 to new build system. (Lukas Winkler)
  • Port debian-multiconfig-gcc-stable to new build system. (Lukas Winkler)
  • Port elektra-ini-mergerequests to new build system. (Lukas Winkler)
  • Port elektra-gcc-configure-debian-nokdbtest to new build system. (Lukas Winkler)
  • Port elektra-gcc-configure-xdgto new build system. (Lukas Winkler)
  • Port elektra-gcc-i386 to new build system. (Lukas Winkler)
  • Port elektra-gcc-configure-debian-musl to new build system. (Lukas Winkler)
  • Docker Registry is cleaned up by our daily buildserver task. (Lukas Winkler)
  • Remove elektra-gcc-configure-debian-nokdbtest test. Instead we are now
    removing write permissions of Elektra's paths to detect if we write to the
    filesystem even though tests are not tagged as such. (Lukas Winkler)
  • Remove elektra-gcc-configure-debian-withspace test. We now test for
    compatibility of spaced build paths during normal tests. (Lukas Winkler)
  • Check for source formatting during early test stages. (Lukas Winkler)
  • Remove the amount of spawned tests via not running a full multiconfig setup for
    the PLUGINS=NODEP config. They did not provide any additional coverage.
    Instead we added a new test checking if PLUGINS=NODEP builds in an minimal
    Docker image. (Lukas Winkler)
  • Speed up coverage data upload. (Lukas Winkler)
  • Fix an issue where file archiving did not happen because of suppressed shell
    expansion (Lukas Winkler)
  • Setup mailing for jenkins (Lukas Winkler)
    • send mail to build@libelektra.org when master fails (Lukas Winkler)
    • parse change list into mail (Lukas Winkler)
    • do not send mails if pipeline run was aborted (Lukas Winkler)


  • Travis now uses the latest version of GCC and Clang to translate Elektra on Linux. (René Schwaiger)

  • Our Travis build job now

    • builds all (applicable) bindings by default again, and
    • checks the formatting of CMake code via cmake-format
      . (René Schwaiger)
  • Some cache issues on the Travis build job for cached haskell sandboxes have been resolved. (Armin Wurzinger)

  • Travis caches downloaded Homebrew packages to improve the reliability of macOS build jobs. (René Schwaiger)

  • Travis is now using Xcode 9.4.1 on macOS 10.13 for most macOS build jobs. (Mihael Pranjić)

  • We added a unique name to each build job, so you can see quickly which configuration caused problems. (René Schwaiger)

  • We now specify custom binding, plugin and tool configuration for jobs via the environment variables:

    • PLUGINS, and
    • TOOLS

    . We also added environment variables for the build configuration options BUILD_FULL, COMMON_FLAGS, ENABLE_ASAN and the command
    used to test the build (TEST_COMMAND). (René Schwaiger)

  • The ASAN build jobs 🍏 Clang ASAN and 🐧 GCC ASAN now only build the kdb tool and the cpp binding. This update ensures, that we
    do not hit the job timeout for public repositories that often.
    (René Schwaiger)

  • We now use the latest version of Ruby (2.5.1) to build and test the Ruby binding/plugin. (René Schwaiger)


As always, the ABI and API of kdb.h is fully compatible, i.e. programs
compiled against an older 0.8 version of Elektra will continue to work
(ABI) and you will be able to recompile programs without errors (API).

Following changes were made:

  • The C++ API was extended with delBaseName().
    This does not affect ABI compatibility, also C++ programs compiled against 0.8.24 and using delBaseName() will work with Elektra 0.8.23 or older.
  • kdbtypes.h now comes with support for C99 types.
  • We added the private headerfiles kdbnotificationinternal.h, kdbioplugin.h. (Thomas Wahringer)
  • The I/O binding header files have been moved a new directory called kdbio.
    For example, instead of including elektra/kdbio_ev.h users of the binding now include elektra/kdbio/ev.h. (Thomas Wahringer)
  • The plugin directoryvalue has changed its behavior, see above.
  • The plugin list changed its configuration, see above.
  • The plugin yamlcpp now gets excluded with too old versions of yamlcpp (Debian Stretch is affected).

The new plugins are:

  • hexnumber
  • yamlsmith
  • zeromqrecv
  • zeromqsend

The new tool is: kdb-find


The website is generated from the repository, so all information about
plugins, bindings and tools are always up to date.


We are currently working on following topics:

  • The hybrid search algorithm for the Key search ksLookup (...) is now in preparation.
    The preparation includes a new KeySet flag KS_FLAG_NAME_CHANGE, this flag will be used by the hybrid search.
    The hybrid search combines the best properties of the binary search and the OPMPHM.
    The hybrid search uses a modified branch predictor to predicts KeySet changes and decides if binary search or OPMPHM would be faster. (Kurt Micheli)


Following persons made in total 1734 commits:

  1 commit  by Mihael Pranjic <mpranj@limun.org>
  2 commits by Thomas Waser <thomas.waser@libelektra.org>
  7 commits by Michael Zronek <michael.zronek@gmail.com>
 12 commits by Kurt Micheli <e1026558@student.tuwien.ac.at>
 17 commits by Peter Nirschl <peter.nirschl@gmail.com>
 21 commits by Klemens Böswirth <k.boeswirth+git@gmail.com>
197 commits by Markus Raab <elektra@markus-raab.org>
102 commits by Thomas Wahringer <thomas.wahringer@libelektra.org>
117 commits by Daniel Bugl <me@omnidan.net>
265 commits by Lukas Winkler <derwinlu+git@gmail.com>
249 commits by Armin Wurzinger <e1528532@student.tuwien.ac.at>
744 commits by René Schwaiger <sanssecours@me.com>

In total there were 792 files changed with 27677 insertions(+) and 39176 deletions(-).

Get It!

You can download the release from here
or GitHub

The hashsums are:

  • name: elektra-0.8.24.tar.gz
  • size: 6130464
  • md5sum: 2e3def7b905f94e1f9f7fa0fe4743189
  • sha1: ff2a9b2d3a5e20a456e272a47fe9fd79ad410428
  • sha256: 454763dd00e95e774a907b26eb59b139cfc59e733692b3cfe37735486d6c4d1d

The release tarball is also available signed by Markus Raab using GnuPG from
here or on

Already built API-Docu can be found online
or GitHub.

Stay tuned!

Subscribe to the
RSS feed
to always get the release notifications.

For any questions and comments, please contact the
issue tracker on GitHub
or Markus Raab by email using elektra@markus-raab.org.

Permalink to this NEWS entry

For more information, see https://libelektra.org

Best regards,
Elektra Initiative