[MacPorts] #24735: tightvnc conflicts with vnc

[MacPorts]

#24735: tightvnc conflicts with vnc
-------------------------------------------+--------------------------------
  Reporter:  macsforever2000@…             |       Owner:  macports-tickets@…                   
      Type:  defect                        |      Status:  closed                               
  Priority:  Normal                        |   Milestone:                                       
 Component:  ports                         |     Version:  1.8.2                                
Resolution:  fixed                         |    Keywords:                                       
      Port:  tightvnc vnc                  |  
-------------------------------------------+--------------------------------

Comment(by ryandesign@…):

 #20199 is a different problem. This ticket is about activate-time
 conflicts, which is what the conflicts keyword was designed for. #20199 is
 about build-time conflicts, which we have no solution for, but which the
 conflicts keyword has been abused for in ports like qt4-mac.

 What solution to this ticket should we employ? We could rename the files,
 but which one? Both? To what? It might be helpful if you could bring this
 conflict to the attention of the developers of both vnc and tightvnc and
 get their input on what the proper solution is. Ideally the proper
 solution would be applied by the developers of those software packages
 directly to their sources.

-- 
Ticket URL: <http://trac.macports.org/ticket/24735#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS