Context Navigation

Changes between Initial Version and Version 1 of Ticket #51619, comment 33

initial	v1
3	3	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.
4	4
5		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.
	5	One thing I didn't check: did you foresee a way to pull in your meta-port, i.e. the appropriate port:qt5 or port:qt55, etc? 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.