Thread Previous • Date Previous • Date Next • Thread Next |
Am 04.02.2015 um 15:35 schrieb Michał Sawicz:
If we are going down that path, the stores responsibilty must be to split up theW dniu 04.02.2015 o 15:16, Zoltán Balogh pisze:One possible side thought for that feature could be to somehow let the app consumer skim the used binaries out from the fat packages. Because a real fat package can get really fat :) imagine an app with 6 or 9 builds in it.Oh yeah, that's for sure, we need to make everything shared as much as possible.
fat package and only deliver the parts required for the specific client.Why should a armhf 15.04 device download binaries for i386 14.10 and i386 15.04.
That is a waste of bandwith AND space on the end users device.... Also packaging a app like that is really not easy even with UI support. I imagine a QtC project with > 10 buildconfigurations is not fun to handle..
Thread Previous • Date Previous • Date Next • Thread Next |