[MacPorts] #55293: set ${prefix} in portindex

MacPorts noreply at macports.org
Thu Nov 16 15:30:01 UTC 2017


#55293: set ${prefix} in portindex
--------------------------+-----------------
  Reporter:  RJVB         |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+-----------------

Comment (by RJVB):

 Hmmm, yes, but in this case that's unavoidable I fear, and already
 introduced a while ago independent of the issue I brought up here.

 If the user choses to install port:qt5x-qtbase (or qt5-kde) and later
 needs to add, say, QtWebEngine, he'd need to install qt5x-qtwebengine (or
 qt5-kde-qtwebengine) and the matching dependencies of that port. So, for
 instance, qt5x-qtlocation and not some other qt5y-qtlocation -- and when
 he installed qt5-kde most Qt components are actually provided by that main
 port.

 This may be novel behaviour, but as I said I don't see how we can do this
 any other way (that doesn't increase complexity enormously at least). We'd
 probably be facing the same thing for ports written in Python or Perl if
 those didn't install to version-specific locations. At the same time those
 ports can use any of the installed Python, Perl (or LLVM or ...) ports
 while only 1 version of Qt5 can be installed and active at a given time
 (and Qt guarantees backwards ABI compatibility).

 The final dependency computation has to run the Portfiles anyways because
 of the build variant selection, no? IOW, build dependencies are host/user
 dependent even if they're not always different from the default?!

 What kind of probem do you think a host-dependent PortIndex could cause?
 They're already OS version dependent and there can be any number of
 PortIndex files, so I'd assume they're already tested for robustness in
 this domain, AND they have to be generated locally anyway.

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


More information about the macports-tickets mailing list