Hello, > What you should do -- if you want to have your "own" configuration (and > use the libgnunetutil configuration parser) -- is to load your > configuration using GNUNET_CONFIGURATION_create/load APIs providing your > own application paths explicitly there. However, that configuration > object must then not be used to interact with GNUnet services. So you'd > basically have two configuration handles: one or your own application > (which you'd use internally), and one which you'd pass to GNUnet APIs.
I've experimented with this approach and managed to find a way that seems to work without particular issues, for clients and services. As such, this case can be closed as not-a-bug. Thanks, A.V. _______________________________________________ Bug-GNUnet mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnunet
