Well, if alien provides the same components of the framework, your module and alien's should be similar in size shouldn't it, as both an xzm module and a txz package uses the xz compression?
What I meant was, since porteus provides the module based approach and mechanism to activate and deactivate modules on the fly, why not split qt into logical modules and activate them when needed? It would also help in a rammod copy2ram scenario.
Even for a developer who just wants to create a widget based application or even to create a QML/Quick application, activating a 74MB module for it is overkill dont you think?
Even Qt provides release sources as submodules (You can see qt 5.9.1 is already released
http://download.qt.io/official_releases ... ubmodules/
Not all applications need heavy modules like qt webkit and webengine.
- A logical split would be qt-base module (that contains qtbase, qtx11-extras and qtsvg) along with qt dependencies (libinput, libxkbcommon, xcb utils) -> This is also the needed dependecies for lxqt
- qt declarative, qt quick controls and qt graphical effects would be the qt-quick module
- qttools, qtscript and headers and .la files exported from the above modules would be the qt-devel module
- Qt Creator built from these modules
I had such a split when I was developing a qt quick application during qt 5.6 days. The module sizes were: qtbase.xzm -> 8.8 MB, qtdevel.xzm -> 12MB, qtquick -> 4MB and qtcreator 16MB. I could also activate a subset of these modules to run the lxqt 0.10 desktop or develop and run widget only applications.
Additional modules could be added as needed (Also, if you remove unneeded libraries from lxqt, they could go into a qt-extra module).
What do you think?