[VeryOld] Keyname overhaul

.github/ISSUE_TEMPLATE.md

@@ -9,17 +9,17 @@ Please provide a step by step guide on how to reproduce the problem here. If pos
 syntax:
 
 ```sh
-kdb set user/tests/hello world
-#> Create a new key user/tests/hello with string "world"
+kdb set user:/tests/hello world
+#> Create a new key user:/tests/hello with string "world"
 
-kdb get user/tests/hello
+kdb get user:/tests/hello
 #> world
 
-kdb get user/does/not/exist
+kdb get user:/does/not/exist
 # RET: 11
-# STDERR: [Dd]id not find key 'user/does/not/exist'
+# STDERR: [Dd]id not find key 'user:/does/not/exist'
 
-kdb rm user/tests/hello
+kdb rm user:/tests/hello
 ```
 
 If your key database (KDB) might influence the outcome, please use `kdb stash`

benchmarks/benchmarks.c

@@ -598,7 +598,7 @@ KeySet * generateKeySet (const size_t size, int32_t * seed, KeySetShape * shape)
 	}
 	for (size_t i = 0; i < root->numberofChildren; ++i)
 	{
-		Key * key = keyNew ("", KEY_END);
+		Key * key = keyNew ("/", KEY_END);
 		if (!key)
 		{
 			printExit ("generateKeySet: Can not create Key");

benchmarks/benchmarks.h

@@ -22,7 +22,7 @@
 
 #include <time.h>
 
-#define KEY_ROOT "user/benchmark"
+#define KEY_ROOT "user:/benchmark"
 
 #define KEY_NAME_LENGTH 1000
 #define NUM_DIR 200

benchmarks/kdb.c

@@ -29,7 +29,7 @@ int main (void)
 	fprintf (stdout, "%s;%s;%s\n", "plugin", "operation", "microseconds");
 	{
 		KeySet * returned = ksNew (0, KS_END);
-		Key * parentKey = keyNew ("user", KEY_END);
+		Key * parentKey = keyNew ("user:/", KEY_END);
 
 		timeInit ();
 		KDB * handle = kdbOpen (parentKey);
@@ -49,7 +49,7 @@ int main (void)
 	for (size_t i = 0; i < NUM_RUNS; ++i)
 	{
 		timeInit ();
-		Key * parentKey = keyNew ("user/benchmark", KEY_END);
+		Key * parentKey = keyNew ("user:/benchmark", KEY_END);
 		KDB * handle = kdbOpen (parentKey);
 		fprintf (stdout, CSV_STR_FMT, "core", "kdbOpen", timeGetDiffMicroseconds ());
 

benchmarks/memoryleak.c

@@ -19,7 +19,7 @@ int main (void)
 	KDB * handles[NUM_RUNS];
 	KeySet * keysets[NUM_RUNS];
 
-	Key * parentKey = keyNew ("user", KEY_END);
+	Key * parentKey = keyNew ("user:/", KEY_END);
 
 	for (size_t i = 0; i < NUM_RUNS; ++i)
 	{

benchmarks/opmphm.c

@@ -2461,7 +2461,7 @@ static void shapefCommonStartEnd (const size_t initSize ELEKTRA_UNUSED, size_t s
 	}
 }
 /**
- * modules, level 1 keys same, one level 2 key stores the modules. Like system/elektra.
+ * modules, level 1 keys same, one level 2 key stores the modules. Like system:/elektra.
  */
 static void * shapeModulesInit (void)
 {
@@ -2496,13 +2496,13 @@ static void shapefModules (const size_t initSize, size_t size ELEKTRA_UNUSED, si
 	uint8_t * assign = &d[3];
 	if (level == 1)
 	{
-		// common start, simulates elektra in system/elektra
+		// common start, simulates elektra in system:/elektra
 		ret->subKeys = 1;
 		ret->label = 0;
 	}
 	else if (level == 2)
 	{
-		// common name, simulates modules in system/elektra/modules
+		// common name, simulates modules in system:/elektra/modules
 		// calculates how many modules have space
 		ret->subKeys = 0;
 		ssize_t remainingSize = initSize;

benchmarks/plugingetset.c

@@ -45,7 +45,7 @@ int main (int argc, char ** argv)
 		KeySet * conf = ksNew (0, KS_END);
 		KeySet * modules = ksNew (0, KS_END);
 		elektraModulesInit (modules, 0);
-		Key * errorKey = keyNew ("", KEY_END);
+		Key * errorKey = keyNew ("/", KEY_END);
 		Plugin * plugin = elektraPluginOpen (pluginname, modules, conf, errorKey);
 		keyDel (errorKey);
 
@@ -69,7 +69,7 @@ int main (int argc, char ** argv)
 		KeySet * conf = ksNew (0, KS_END);
 		KeySet * modules = ksNew (0, KS_END);
 		elektraModulesInit (modules, 0);
-		Key * errorKey = keyNew ("", KEY_END);
+		Key * errorKey = keyNew ("/", KEY_END);
 		Plugin * plugin = elektraPluginOpen (pluginname, modules, conf, errorKey);
 		keyDel (errorKey);
 		plugin->kdbSet (plugin, ks, setKey);

benchmarks/storage.c

@@ -35,7 +35,7 @@ static int benchmarkOpenPlugins (void)
 		modules[i] = ksNew (0, KS_END);
 		elektraModulesInit (modules[i], 0);
 		KeySet * conf = ksNew (0, KS_END);
-		Key * errorKey = keyNew ("", KEY_END);
+		Key * errorKey = keyNew ("/", KEY_END);
 		Plugin * plugin = elektraPluginOpen (pluginNames[i], modules[i], conf, errorKey);
 
 		const Key * metaWarnings = keyGetMeta (errorKey, "warnings");
@@ -104,7 +104,7 @@ int main (int argc, char ** argv)
 		init (argc, argv);
 
 		Plugin * plugin = plugins[i];
-		Key * parentKey = keyNew ("user/benchmarks/storage", KEY_VALUE, tmpfilename, KEY_END);
+		Key * parentKey = keyNew ("user:/benchmarks/storage", KEY_VALUE, tmpfilename, KEY_END);
 
 		for (size_t run = 0; run < NUM_RUNS; ++run)
 		{

doc/METADATA.ini

@@ -1060,7 +1060,7 @@ example=internal/ini/parent could be the name for internal parent
 status= idea
 description= states where a key comes from if it is not from an ordinary
 	persistent configuration. E.g. hardware (queries)
-	e.g. system/sw/xorg/current/monitor might have "source" metadata if it
+	e.g. system:/sw/xorg/current/monitor might have "source" metadata if it
 	is queried from hardware and not from configuration file.
 
 [dependency/control]

doc/TESTING.md

@@ -83,15 +83,15 @@ You have some options to avoid running them as root:
 
    ```sh
    kdb mount-info
-   echo `kdb sget system/info/elektra/constants/cmake/CMAKE_INSTALL_PREFIX .`/`kdb sget system/info/elektra/constants/cmake/KDB_DB_SPEC .`
-   echo `kdb sget system/info/elektra/constants/cmake/KDB_DB_SYSTEM .`
+   echo `kdb sget system:/info/elektra/constants/cmake/CMAKE_INSTALL_PREFIX .`/`kdb sget system:/info/elektra/constants/cmake/KDB_DB_SPEC .`
+   echo `kdb sget system:/info/elektra/constants/cmake/KDB_DB_SYSTEM .`
    ```
 
    Then change the permissions:
 
    ```sh
-   chown -R `whoami` `kdb sget system/info/elektra/constants/cmake/CMAKE_INSTALL_PREFIX .`/`kdb sget system/info/elektra/constants/cmake/KDB_DB_SPEC .`
-   chown -R `whoami` `kdb sget system/info/elektra/constants/cmake/KDB_DB_SYSTEM .`
+   chown -R `whoami` `kdb sget system:/info/elektra/constants/cmake/CMAKE_INSTALL_PREFIX .`/`kdb sget system:/info/elektra/constants/cmake/KDB_DB_SPEC .`
+   chown -R `whoami` `kdb sget system:/info/elektra/constants/cmake/KDB_DB_SYSTEM .`
    ```
 
    After that all test cases should run successfully as described above.
@@ -195,7 +195,7 @@ are expected to be in the README.md of the plugin.
 - should not run, if `ENABLE_KDB_TESTING` is OFF.
 - should only write below
   - `/tests/<testname>` (e.g. `/tests/ruby`) and
-  - `system/elektra` (e.g. for mounts or globalplugins).
+  - `system:/elektra` (e.g. for mounts or globalplugins).
 - Before executing tests, no keys must be present below `/tests`.
   The test cases need to clean up everything they wrote.
   (Including temporary files)
@@ -323,13 +323,13 @@ cp ~e/src/plugins/ini/ini/* testcase_dir
 Fewer files is better. Then run, for example:
 
 ```sh
-LD_LIBRARY_PATH=`pwd`/lib /usr/src/afl/afl-2.52b/afl-fuzz -i testcase_dir -o findings_dir bin/kdb import user/tests ini
+LD_LIBRARY_PATH=`pwd`/lib /usr/src/afl/afl-2.52b/afl-fuzz -i testcase_dir -o findings_dir bin/kdb import user:/tests ini
 ```
 
 Check if something is happening with:
 
 ```sh
-watch kdb export user/tests
+watch kdb export user:/tests
 ```
 
 ### ASAN

doc/VERSION.md

@@ -9,10 +9,10 @@ information.
 The same information can be retrieved at run-time using
 
 ```
-system/elektra/version/constants/KDB_VERSION
-system/elektra/version/constants/KDB_VERSION_MAJOR
-system/elektra/version/constants/KDB_VERSION_MICRO
-system/elektra/version/constants/KDB_VERSION_MINOR
+system:/elektra/version/constants/KDB_VERSION
+system:/elektra/version/constants/KDB_VERSION_MAJOR
+system:/elektra/version/constants/KDB_VERSION_MICRO
+system:/elektra/version/constants/KDB_VERSION_MINOR
 ```
 
 This is the API to programs using Elektra. Its interface

doc/VISION.md

@@ -27,13 +27,13 @@ as desired.
 Either by either invoking [command-line tools](/doc/help/kdb.md):
 
 ```sh
-kdb set system/sw/samba/#0/current/global/workgroup MYGROUP
+kdb set system:/sw/samba/#0/current/global/workgroup MYGROUP
 ```
 
 Also by importing an INI file with the information:
 
 ```ini
-kdb import system/sw/samba/#0/current ini << HERE
+kdb import system:/sw/samba/#0/current ini << HERE
 [global]
 workgroup=MYGROUP
 HERE
@@ -49,7 +49,7 @@ with neither code generation nor error handling):
 int main ()
 {
 	ElektraError* error;
-	Elektra * elektra = elektraOpen ("system/sw/samba/#0/current", 0, &error);
+	Elektra * elektra = elektraOpen ("system:/sw/samba/#0/current", 0, &error);
 	elektraSetString (elektra, "global/workgroup", "MYGROUP", &error);
 	elektraClose (elektra);
 }
@@ -62,7 +62,7 @@ Or using some interpreted language like Python
 import kdb
 k = kdb.KDB()
 ks = kdb.KeySet()
-s = "system/sw/samba/#0/current"
+s = "system:/sw/samba/#0/current"
 k.get (ks, s)
 ks.append(kdb.Key(s+"/global/workgroup", kdb.KEY_VALUE, "MYGROUP"))
 k.set (ks, s)
@@ -75,7 +75,7 @@ change a configuration value.
 Key-value access in [puppet-libelektra](https://puppet.libelektra.org):
 
 ```
-kdbkey {'system/sw/samba/#0/current/global/workgroup':
+kdbkey {'system:/sw/samba/#0/current/global/workgroup':
 	ensure => 'present',
 	value => 'MYGROUP'
 }
@@ -84,7 +84,7 @@ kdbkey {'system/sw/samba/#0/current/global/workgroup':
 Key-value access in Chef:
 
 ```
-kdbset 'system/sw/samba/#0/current/global/workgroup' do
+kdbset 'system:/sw/samba/#0/current/global/workgroup' do
 	value 'MYGROUP'
 	action :create
 end
@@ -99,12 +99,12 @@ Key-value access in Ansible:
   tasks:
     - name: set workgroup
       elektra:
-        key: "system/sw/samba/#0/current/global/workgroup"
+        key: "system:/sw/samba/#0/current/global/workgroup"
         value: "MYGROUP"
 ```
 
 In all these examples, we have set
-`system/sw/samba/#0/current/global/workgroup` to `MYGROUP`.
+`system:/sw/samba/#0/current/global/workgroup` to `MYGROUP`.
 
 ## Application Integration
 
@@ -148,7 +148,7 @@ shown above can be used. To make mounting more simple, we introduced an
 extra tool:
 
 ```sh
-kdb mount /etc/samba/smb.conf system/sw/samba/#0/current ini
+kdb mount /etc/samba/smb.conf system:/sw/samba/#0/current ini
 ```
 
 Mounting can also be done via configuration management
@@ -157,12 +157,12 @@ tools.
 Mounting in puppet-libelektra:
 
 ```
-kdbmount {'system/sw/samba/#0/current':
+kdbmount {'system:/sw/samba/#0/current':
 	ensure => 'present',
 	file => '/etc/samba/smb.conf',
 	plugins => 'ini'
 }
-kdbkey {'system/sw/samba/global/log level':
+kdbkey {'system:/sw/samba/global/log level':
 	ensure => 'absent'
 }
 ```
@@ -176,7 +176,7 @@ Mounting in Ansible:
   tasks:
     - name: set workgroup
     elektra:
-      mountpoint: system/sw/samba
+      mountpoint: system:/sw/samba
       file: /etc/samba/smb.conf
       plugins: ini
 ```
@@ -209,7 +209,7 @@ kdb set-meta /sw/samba/#0/current/global/workgroup description "This controls wh
 Key-value specifications in [puppet-libelektra](https://puppet.libelektra.org):
 
 ```
-kdbkey {'system/sw/samba/#0/current/global/workgroup':
+kdbkey {'system:/sw/samba/#0/current/global/workgroup':
 	ensure => 'present',
 	check => {
 		'type' => 'string',
@@ -224,7 +224,7 @@ kdbkey {'system/sw/samba/#0/current/global/workgroup':
 ```
 
 Note, that the specification (in both examples above) actually lands up in
-`spec/sw/samba/#0/current/global/workgroup`. The unique path to the
+`spec:/sw/samba/#0/current/global/workgroup`. The unique path to the
 configuration setting is `/sw/samba/#0/current/global/workgroup`, but
 the specification gets written to the [namespace](/doc/tutorials/namespaces.md)
 `spec`, while the system-configuration gets written to the namespace `system`.

doc/decisions/bootstrap.md

@@ -4,7 +4,7 @@
 
 Currently the default backend (default.ecf) will also be used for bootstrapping. There are two problems with this approach:
 
-1. Thus the default backend first will be read with parentKey `system/elektra` and later with parentKey `system`, it needs to store absolute paths and thus won't work with the current INI plugin
+1. Thus the default backend first will be read with parentKey `system:/elektra` and later with parentKey `system:/`, it needs to store absolute paths and thus won't work with most of the plugins (except dump).
 2. When `system` is large without mount points, everything is reread twice during bootstrapping.
 
 ## Constraints
@@ -19,7 +19,7 @@ Currently the default backend (default.ecf) will also be used for bootstrapping.
 
 ## Considered Alternatives
 
-- Implement a hack so that `system/elektra` is actually read as `system`. (Will not solve problem 2.)
+- Implement a hack so that `system:/elektra` is actually read as `system:/`. (Will not solve problem 2.)
   - Its a hack.
   - Its confusing and does not play well with persistent data with relative key names.
 - Split up without compatibility mode: would need to migrate all mount points by exporting (with old version!) and then importing (with new version!)
@@ -33,10 +33,8 @@ The default backend reading `default.ecf` is only relevant as long as no root ba
 
 Algorithm:
 
-1. try to get system/elektra using the file elektra.ecf (KDB_DB_INIT)
-2. if it works, mount the init backend to system/elektra (non-fallback mode)
-3. if it fails (== 0 or == -1), try default.ecf as fallback
-4. if the fallback works (i.e. keys are present in system/elektra), mount the default backend to system/elektra (fallback mode)
+1. try to get system:/elektra using the file elektra.ecf (KDB_DB_INIT)
+2. if it works, mount the init backend to system:/elektra
 
 ## Rationale
 
@@ -46,7 +44,6 @@ Algorithm:
 
 ## Implications
 
-- Fallback mode should be removed with 1.0
 - added scripts/upgrade-bootstrap
 
 ## Related Decisions
@@ -56,4 +53,4 @@ Algorithm:
 to upgrade to new system, either:
 
 - touch /etc/kdb/elektra.ecf (loses old mount points)
-- or do kdb export system/elektra/mountpoints, kdb rm -r system/elektra/mountpoints, kdb import system/elektra/mountpoints
+- or do kdb export system:/elektra/mountpoints, kdb rm -r system:/elektra/mountpoints, kdb import system:/elektra/mountpoints

doc/decisions/global_plugins.md

@@ -36,7 +36,7 @@
 Configuration will be in arrays below the keys:
 
 ```
-system/elektra/globalplugins
+system:/elektra/globalplugins
                              /prerollback
                              /rollback
                              /postrollback
@@ -199,7 +199,7 @@ getresolver/after/once
 Its useful to have some important global plugins, e.g. locking by default.
 See #690.
 
-Internal list to be used when no system/elektra/global_mountpoints/ exists.
+Internal list to be used when no system:/elektra/global_mountpoints/ exists.
 
 State diagrams of plugins need to be redrawn to also include global plugin
 states.
@@ -215,9 +215,9 @@ states.
 ## Implementation Hints
 
 - add `Plugin *globalPlugins [NR_OF_PLUGINS]` to `_KDB`
-- during `kdbOpen`, `system/elektra/globalplugins/` is read and plugins are constructed and placed into `globalPlugins`.
+- during `kdbOpen`, `system:/elektra/globalplugins/` is read and plugins are constructed and placed into `globalPlugins`.
 - In kdbGet and kdbSet hooks execute one of these plugins
 - by default
-  - the plugins are all the same `list` plugins, and their subplugins are executed, when `system/elektra/globalplugins/_` states they should be executed
+  - the plugins are all the same `list` plugins, and their subplugins are executed, when `system:/elektra/globalplugins/_` states they should be executed
   - a `lock` plugin that executes at begin and end of kdbGet and kdbSet, respective, i.e. postrollback preget postget preset postcommit
   - the `lock` plugin contains the code currently found in resolver