[MacPorts] #61033: zeek conflicts with caf

MacPorts noreply at macports.org
Thu Aug 20 20:34:50 UTC 2020


#61033: zeek conflicts with caf
-------------------------+-------------------------
  Reporter:  ryandesign  |      Owner:  Schamschula
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.99
Resolution:  fixed       |   Keywords:
      Port:  zeek caf    |
-------------------------+-------------------------

Comment (by ryandesign):

 That is not the fix I was looking for. zeek and caf continue to conflict.
 If both ports will continue to exist and provide caf files, then you need
 to declare the conflict between the ports using the `conflicts` keyword in
 both ports.

 Why must zeek use a bundled caf? Can't it use the one from the caf port?

 Alternately, since you appear to have originally added caf to MacPorts
 just so that it could be a dependency of zeek, and now nothing depends on
 it, consider discontinuing the caf port and marking it `replaced_by zeek`.

-- 
Ticket URL: <https://trac.macports.org/ticket/61033#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list