New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #24735 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

tightvnc conflicts with vnc

Reported by: macsforever2000@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: ryandesign@…
Port: tightvnc vnc

Description (last modified by macsforever2000@…) (diff)

tightvnc and vnc conflict on activate. They both want the file /opt/local/bin/vncpasswd.

Change History

comment:1 Changed 4 years ago by macsforever2000@…

  • Description modified (diff)

comment:2 Changed 4 years ago by ryandesign@…

  • Status changed from new to closed
  • Cc ryandesign@… added
  • Resolution set to fixed

Marked as conflicting in r67391.

comment:3 Changed 4 years ago by macsforever2000@…

This does not solve the problem though. I think this ticket should be re-opened until a fix can be found. See also #20199 which remains open.

comment:4 Changed 4 years ago 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.

Note: See TracTickets for help on using tickets.