#16525: ufraw dcraw file conflict ---------------------------------+------------------------------------------ Reporter: dersh@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: fixed | Keywords: Port: ufraw dcraw | ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * status: assigned => closed * resolution: => fixed Comment: I've now investigated. ufraw provides a modified version of the same software provided by the dcraw port. And the README (in ufraw 0.16) says: Do not package the executables generated by by --enable-extras. These extras are there for testing the code during development. They are of no interest to end user. Specifically, if you want to package dcraw, you should use Dave's original code and not UFRaw's modified code. So in r62098, while updating ufraw to 0.16, I removed the --enable-extras configure arg so that ufraw and dcraw will no longer conflict. I added a dependency on dcraw because the description of the ufraw port says it uses the dcraw program. In r62099 I removed the post-activate message from dcraw about the ufraw conflict. -- Ticket URL: <http://trac.macports.org/ticket/16525#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS