[MacPorts] #38005: wireshark doesn't build without libpng

[MacPorts]

#38005: wireshark doesn't build without libpng
-----------------------------------------+------------------------------
  Reporter:  jkh@…                       |      Owner:  opendarwin.org@…
      Type:  defect                      |     Status:  reopened
  Priority:  Normal                      |  Milestone:
 Component:  ports                       |    Version:  2.1.3
Resolution:                              |   Keywords:
      Port:  wireshark, wireshark-devel  |
-----------------------------------------+------------------------------

Comment (by larryv@…):

 Replying to [comment:8 ricci@…]:
 > I disagree.  For example, wireshark depends on glib2.  In turn, glib2
 > depends on libxml2, which, in turn, depends on zlib.  What I'm hearing
 > is that we should include zlib as a direct dependency of wireshark
 > because something wireshark depends on depends on something which
 > depends on zlib.  I think that's completely wrong, wireshark should
 > not care what it's direct dependencies need.

 Ideally yes, wireshark should not care about dependencies of dependencies.
 The issue is that its build system seems to make it start caring, even
 though we don’t want it to.

 > So far as users breaking a port by removing the dependencies of
 > dependencies, they'd have to force the removal which is known to be
 > a way to break things, whether the dependencies are direct or
 > indirect.

 Scenario:

 1. `wireshark` opportunistically links to `libxml2` but doesn’t declare a
 dependency on it.
 2. `glib2` stops depending on `libxml2` (hypothetically). `libxml2` might
 be a leaf now because `wireshark` did not declare a dependency on it.
 3. User uninstalls leaves.
 4. `wireshark` breaks.

 > I do agree that it is a problem if a port is linking in something
 > which is not somewhere in the dependency chain, and that those should
 > be fixed.

 Right; this is what the others are asserting is happening. It’d be best if
 `wireshark` didn’t link to things willy-nilly.

 (I personally have not looked into it.)

-- 
Ticket URL: <https://trac.macports.org/ticket/38005#comment:9>
MacPorts <https://www.macports.org/>
Ports system for OS X