| 18 | | Basically, yes. If ever there's an opportune moment for such a thing it'd be one like now, I guess. |
| | 18 | Basically, yes. If ever there's an opportune moment for such a thing it'd be one like now, I guess - especially if the bump to Qt 5.4.2 is still waiting. |
| | 19 | |
| | 20 | PS: now might also be a good time to decide whether or not you want to follow Bradley's suggestion to re-integrate the sqlite3 plugin into the main port. The ''main port actually depends on it'', and Qt's build process supports building it along with the rest. (It's actually more complicated to build those plugins separately.) |
| | 21 | |
| | 22 | PS2: about that chewing-through: that can be reduced roughly in half by removing qtwebengine from the standard Qt5.4+ build (reduces the software archive by some 35% too; the installed footprint probably by even more). |
| | 23 | QtWebengine is new in Qt 5.4, so it was rather natural to handle that by moving it to a dedicated subport. |
