[MacPorts] #58441: "port upgrade libgcc8" pulls libgcc9 instead (and fails, of course). Also affects gcc8 port

MacPorts noreply at macports.org
Wed May 8 19:14:33 UTC 2019


#58441: "port upgrade libgcc8" pulls libgcc9 instead (and fails, of course). Also
affects gcc8 port
-------------------------+--------------------
  Reporter:  mouse07410  |      Owner:  (none)
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:  worksforme  |   Keywords:
      Port:  libgcc8     |
-------------------------+--------------------

Comment (by mouse07410):

 > The way this is set up now, the port people should be installing (and
 the one that is dependencied in other ports) is {{{libgcc}}}.

 I'm not sure I buy it, as I doubt a user would care to install a specific
 **{{{lib}}}**{{{gccX}}}. A user may care to install a specific
 **{{{gcc}}}**{{{X}}}. For example, I wanted to upgrade {{{gcc8}}}.
 {{{libgcc8}}} was something that this port pulled as its dependency, and
 when it works OK the user doesn't even notice its existence.  IMHO, a user
 may want to explicitly (re-)install this port only to repair something
 broken.

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


More information about the macports-tickets mailing list