Changes between Initial Version and Version 1 of Ticket #53230, comment 3


Ignore:
Timestamp:
Jan 6, 2017, 10:19:23 AM (8 years ago)
Author:
RJVB (René Bertin)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #53230, comment 3

    initial v1  
    88
    99must continue to do so, and must build and install regardless of which Qt5 port is installed. The same applies to KF5 ports: I do not intend to support using them with port:qt5, but they should build (for the most part at least) and run (to some extent). So KF5 ports will express only a preference on port:qt5-kde, not a hard dependency (see below for what that means).
    10  
     10
     11A crucial point: for most Qt5-dependent, non-KDE-related ports it ultimately wouldn't really matter if they function only with port:qt5 (say, Qt Creator) but there are a few ports that are dependencies of KF5 (port:qca-qt5, the future port:qgpgme, port:opencv+qt5, port:poppler-qt5 to name a few).
     12
    1113The main difficulty here was the breaking up of port:qt5 into Qt5 component subports. With port:qt5-kde I split off only the huge QtWebEngine and kept the rest bundled like port:qt4-mac is; port:qt5 was later converted to provide each component in subports. This has been solved by the introduction of a `qt5.depends_component` procedure that ports can use to declare dependencies on those subports, and which will translate into "adaptive depspecs".
    1214