Comment 21 for bug 1006743

Thanks for the clarifications. This gets really complicated if you consider that we should be able to run DNS proxy manually from the command line and automatically from /etc/init.d/ in a binary installation. Rather than trying to live along with DNS masq, I would suggest living without it to make things less complicated:

1. Remove all dnsmasq integration from the python code. If HIP dns proxy cannot bind to port, exit with some warnings:

"Port xx is occupied. Please remove dnsmasq, or any other software, if you're running it or change the default invocation parameter --xx in /etc/default/hipdnsproxy."

2. Modify Debian and Fedora packaging to mark "dnsmasq" as a conflicting package.
* debian/control (hipl-dnsproxy package): Conflicts: dnsmasq (see http://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts)
* trunk/packaging/hipl.spec (dnsproxy package): Conflicts dnsmasq (see http://www.rpm.org/max-rpm/s1-rpm-depend-manual-dependencies.html)

3. Test installation at least with Ubuntu with dnsmasq installed.

Does this work for you?