advice needed on handling network port conflicts

[Eric Cooper <ecc@cmu.edu>]

I've written a proxy server (approx) that is intended to be a drop-in
replacement for apt-proxy.  Sites that use apt-proxy are likely to
have lots of http://foo:9999/...  lines in the /etc/apt/sources.list
files on multiple client machines.  To avoid having to edit all those
files, approx also listens to port 9999 by default.

But if apt-proxy is still installed and running when apt-proxy starts
up, it will fail because the port is in use.  Should I make the approx
package conflict with apt-proxy?  Both packages allow the port to be
changed to something else, so it's not impossible for them to coexist
(just difficult in their default configurations).  Any suggestions
or policy pointers here would be appreciated.

-- 
Eric Cooper             e c c @ c m u . e d u