I finally got around to trying a recent freenet build, from clean, with a
"--config freenet.ini"  configuration file.  No wonder people are
complaining about so much brokenness on Windows.  Since when have %s been
prepended to 'default settings' in the conf file?  What does this mean for
anyone trying to *use* the conf file (e.g. windows frontends)?  If %s are
going to be prepended to break freenet on Windows you may as well remove the
"[Freenet node]" header which was originally added only to assist Windows
compatibility :-)

Does it mean -  search for "clientPort=" and if that isn't found search for
"%clientPort="?  Or does it, more likely, mean search for "clientPort=" and
if that isn't found use the node's default?

If the latter, which I presume because of the conf file comment of "(so they
don't linger when we want to change the default settings)", is the
recommended way for such a frontend app to query the node for its defaults
to do something like freenet.config.Setup freenet.defaults --silent and
parse that?

d


_______________________________________________
devl mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl

Reply via email to