> Am 10.05.2015 um 21:30 schrieb "rpzrpz...@gmail.com" <rpzrpz...@gmail.com>:
>
> Oliver:
>
> I took your advice to heart.
>
> I think there is a happy middle ground using scripts.
>
> During in-house development, I can send everyone a given app with a
> fully self contained bundle. Ultimately, this will satisfy store
> requirements.
>
> But for in-house development, 2 script files can run macdeployqt,
> extract and compress the binary inside the testapp.app file, and place
> the smaller file onto the DropBox distribution directory for over the
> internet distribution.
In-House vs Dropbox vs Internet distribution? "Smaller file" = your
application?
> On the user side, they can run a script to import the compressed binary
> into the proper testapp.app file on their local machine.
Users = "they" = Testers? In-house testing? Why "internet distribution" and the
need for "macdeployqt"?
I must confess you left me confused here ;)
>
> This will avoid the repeated download of the massive QT5 libraries and
> frameworks everytime we ship a new version of the application.
>
> And it will not break the protocol of using self contained bundles for
> applications.
But one thing's for sure: if you mean "it" as in "running scripts in order to
fetch some dependencies (Qt framework)" then this very well violates the Mac
App Store rules. There is no way you can have a Mac App Store running a script
to fetch Qt frameworks from some "shared Dropbox folder" or "from the Internet".
And the same goes for updates: each update must be fully self-contained, means:
with all necessary (Qt) frameworks (it is well possible that the Mac App Store
uses a "diff update mechanism, not sure).
For everything else you can do what you want, but I still fail why you'd want
to have scripts for "in-house testing": I mean, "in-house" = fast intranet -
right? ;)
But if you really mean Joe iAverage Mac user to take part in some "test
campaign": don't expect them to know how to even open the Terminal application,
let alone executing scripts ;)
Cheers,
Oliver
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest