> I haven't filed the bug report, but I did take a look at the source code > today. Making it possible to have port number configurable with didiwiki > was trivial. Patch attached.
This has been applied in version 0.5-4 of DidiWiki. > Maybe my patch is too simple? It's unexpected behaviour that it takes > the next available when giving a occupied port as it's argument. I've changed this also. Didiwiki no longer uses the next available port if it can't bind to the specified port. I've updated the documentation to reflect this change. > When it comes to #305379 in the Debian BTS, I'm not sure if I > consider this work around in another package to solve it. But feel > free to convince me. Likewise. :-) -- hanna m. wallach http://join-the-dots.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
