The Qt build system assumes that when building a module against a release
build of Qt, syncqt was already run at package creation time. So we have to
run syncqt when creating source packages.

This patch changes the syntax to separate the file name base from the
package version to use.

Change-Id: I48897d52a917194be6662a26268ad403883ed9e0
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

* Add a .tag file to the archive that contains the sha1 the package was created from. This is useful for diagnostics.
* Use bash and enforce error handling (it's easy to accidentally include bashisms)

Change-Id: I8141b10d50bbf55a470d5a84ed0ae801742b57dc
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Change-Id: I14dbc2d4770cb0efe9a227e4f113e83c50e00283
Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Change-Id: Id794add1267ebea804b050bb50e232bcf5f7dd13
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

The || true syntax does not work on Windows.

Also, normalize the paths to the underlying OS style.

Change-Id: Ie13d2646fe239fccb9ab7b558a6c8d56b779b206
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Working directory can be wrong when calling getChromiumSrcDir.
On Windows cwd is inside Chrome source directory when it called
from repack_locales.py that causes git config to return empty
value. This causes the function to fall back to snapshot directory
even if upstream is used.

Changing cwd to qtwebengine_root, running git config and restoring
original cwd resolves the problem.

Change-Id: I1bef84ce791f63d3c9e7d6c9506e99c0c53cfc3e
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Building on top of the repacking of .pak files, we now ship
the whole array of repacked locales and pick the appropriate one at runtime.

Change-Id: I0096e3eac6a1fc83885fd11e0fa55a746f8e45d8
Reviewed-by: Andras Becsi <andras.becsi@digia.com>