[MacPorts] #51619: qt5.depends_component procedure
MacPorts
noreply at macports.org
Sun Jan 1 17:39:59 UTC 2017
#51619: qt5.depends_component procedure
---------------------------+----------------------
Reporter: RJVB | Owner: mkae
Type: enhancement | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: qt5, qt5-kde |
---------------------------+----------------------
Comment (by RJVB):
Want, want, want ... my point is a bit that we don't yet have a clear
picture of what we want ... in terms of best compromise. I think it's best
to keep things as simple as possible, and for now that might indeed mean
not bothering with a port that doesn't yet exist.
The main thing now is to have a qt5.depends_component function that works
for your port so that dependent ports can start using it to ease the
integration of port:qt5-kde. In the future that function can be refactored
as needed so that it works with all possible Qt5 ports, without changing
the API of course.
One thing I didn't check: did you foresee a way to pull in your meta-port?
My proposal did that with `qt5.depends_component qt5`, and that syntax is
in fact used in port:py-pyqt5 (with a minimal embedded copy of
qt5.depends_component). In my mind this means "all of Qt5 except WebKit
and WebEngine" because they're so big and the latter is a replacement of
the former. But we could also agree on `qt5.depends_component all` which
would include all subports.
--
Ticket URL: <https://trac.macports.org/ticket/51619#comment:33>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list