[MacPorts] #51707: Octave needs to depend on gcc minor version number

MacPorts noreply at macports.org
Mon Aug 8 08:15:38 PDT 2016


#51707: Octave needs to depend on gcc minor version number
-------------------------+------------------------
  Reporter:  MacPorts@…  |      Owner:  mcalhoun@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.4
Resolution:              |   Keywords:
      Port:  octave      |
-------------------------+------------------------

Comment (by ryandesign@…):

 Replying to [ticket:51707 MacPorts@…]:
 > For details, see [https://savannah.gnu.org/bugs/?41520]
 >
 > The upshot is that Octave needs to depend explicitly on the minor
 version number of gcc so that octave gets rebuilt when upgrading from gcc
 5.3 to 5.4, etc.

 MacPorts does not have the capability to declare a dependency on a version
 of a port, only on a port as a whole. If octave requires this, then the
 developer of octave-devel would have to manually increase its revision
 whenever a new version of gcc is released. octave-devel has variants for
 gcc5, gcc6 and gcc7, and since the developer of octave-devel does not know
 which of those variants the user has chosen, presumably this means the
 developer of octave-devel would need to increase its revision whenever a
 new version of either gcc5 or gcc6 or gcc7 is released. If snapshots count
 as new versions, then new versions of gcc7 are released every week. So
 this is really not a reasonable situation, and it is not reasonable for
 octave to care about the minor revision of the compiler. The developers of
 octave should fix this.

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


More information about the macports-tickets mailing list