Our Boot to Qt images are without a doubt one of the most valuable features in Qt for Device Creation product.
Being at the front-line with leads/prospects/customers, as a pre-sales engineer, I get a lot of positive feedback about Boot to Qt: it is very convenient, it does save lots of time, and it is very helpful for teams without embedded experience in general. Moreover, some of our customers are actually using Boot to Qt images in production, even though we advised them against doing so.
And one of the most common feature requests we get is to have a package manager included into images: APT (apt-get) or something similar. In addition to that, pip (package manager for Python) is also requested quite often (we actually have Python itself included, so it's rather weird not to have pip too).
Since Boot to Qt images originally were about getting stared faster and making developer's life easier, having the ability to install additional tools or Python packages in Boot to Qt images makes all the sense. At the same time I understand that we are unlikely to be eager of becoming yet another Linux distribution as maintaining packages repositories would require certain efforts/resources to be allocated.
Document existing opkg format and how to use it.
|Document the used opkg format in B2Qt||Closed|