Am Freitag, 14. Juli 2006 00:33 schrieb Patrice Dumas: > Hello, > > Given that the selection of the default backend through a link is broken > on platforms where a proper namespace is required, I propose dropping > the libelektra-default.so link. There would still be the possibility to use > the KDB_BACKEND environment variable which seems to be more portable to > me.
KDB_BACKEND is some kind of hack to make it possible for a special application to use another location for configuration. Thus we are trying to introduce a unified configuration hierachy and not a per-application the backend should be the choice of the administrator. Symbolic link is the better way then. If you really want you can set KDB_BACKEND all the time, but there should be a valid -default backend for kdbOpenDefault() in security relevant applications. I would anyway suggest multiple backends at once, with the possiblity to mount backends to any place in the hierachy. But some more work is needed for that (e.g. recursive implementation in kdbGetChildKeys, not in backends). thank you Markus Raab ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Registry-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/registry-list
