[MacPorts] #57794: port:wget needs depspecs for metalink and gpgme (or drop --with-metalink)

MacPorts noreply at macports.org
Wed Dec 19 19:01:17 UTC 2018


#57794: port:wget needs depspecs for metalink and gpgme (or drop --with-metalink)
---------------------+------------------------
  Reporter:  RJVB    |      Owner:  ryandesign
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:
      Port:  wget    |
---------------------+------------------------

Comment (by RJVB):

 That's nice but no guarantee that all dependencies found are indeed direct
 dependencies, or even required (used) dependencies. The link editor simply
 adds references to all shared libraries you tell it to include, and there
 are probably a few (or more) that are private dependencies of other
 dependencies. That's especially true in my experience when pkgconfig is
 used, which doesn't bother with subtleties like "on Mac you don't need to
 include the libraries this requested library depends on" (generally you do
 need them on Linux).

 Case in point: you found libassuan as a dependency, but the {{{fgrep -i
 assuan -R `port work wget`}}} doesn't give a single hit.

 FWIW, I prefer to keep depspec lists as short as possible with my own
 ports. If I depend on port:A which depends on port:B (and port:C) then I
 prefer to let port:A take care of getting its dependencies on B and C
 right. So rather than looking at what is actually linked to a port's
 binaries I look first and foremost at what configure or cmake tell me
 (easier with the former than with the latter).
 Of course, as a user I'm sometimes annoyed when I find out that some port
 with seemingly few dependencies actually needs a whole lot more, but what
 can you do :)

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


More information about the macports-tickets mailing list