#24735 closed defect (fixed)
tightvnc conflicts with vnc
| Reported by: | mf2k (Frank Schima) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.2 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | tightvnc vnc |
Description (last modified by mf2k (Frank Schima))
tightvnc and vnc conflict on activate. They both want the file /opt/local/bin/vncpasswd.
Change History (4)
comment:1 Changed 14 years ago by mf2k (Frank Schima)
| Description: | modified (diff) |
|---|
comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:3 Changed 14 years ago by mf2k (Frank Schima)
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 14 years ago by ryandesign (Ryan Carsten Schmidt)
#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.
Marked as conflicting in r67391.