This option initializes the upstream chromium repository
and additionally to the submodules needed for the matching
OS it also clones submodules needed for Android.

Change-Id: I1df84973aabc10f5c839bc4e3db7c6024f2c5145
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This fixes the ssh error where scp tried to connect to the default
port 22 which timed out.

Change-Id: I7914fafbc3f82eb2c68d52dffb6579d98bcfedd1
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This patch adds --upstream (-u) and --snapshot (-s) flags to the
init-repository script which make it possible to choose the
Chromium sources to use when building QtWebEngine. The default
is to use the upstream submodules.
This option is persisted with git config and used throughout the
build system.
This patch also keeps support for the CHROMIUM_SRC_DIR env
variable which can be used to specify external Chromium
sources which are assumed to be set up for the build and
thus left untouched by the script.

Change-Id: Ic83984199770076f90867f1b22a63b220bfe7359
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This is needed to prevent .gitmodules changes
from showing up when using the upstream repositories.
It will also prevent changes in submodules from showing
up and being added to a commit by accident.

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

The regular workflow now is just to clone the qtwebengine repository
and then execute the following commands.
  git submodule init && git submodule update --recursive && qmake && make
This will also clone a submodule called 3rdparty which contains the
chromium and ninja sources without pulling in further submodules
and without a complete history.

Developers that do want to have a complete chromium checkout instead
should not use the above command sequence.
Instead they should just clone qtwebengine, execute the
init-repository.py script, run qmake and make.
The init-repository.py script will then checkout the complete
chromium sources into a subdirectory called 3rdparty_upstream.
The location of these sources will be picked up by qmake automatically.

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

Split out the Submodule class and related functions from
init-repository.py into a separate python module git_submodule.py.
This is necessary in order to reuse the code for the export script.

The export_from_git.py script can be used to export files
from a git repository into an arbitrary directory.
It spiders submodules and applies some pattern matching to remove
unwanted files.
This script can be used to create flattened chromium snapshots
to be used in our CI system.

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

With this patch init-repository.py will also abort uncommited
git am/merge/rebase sessions and it will do a git reset --hard
on every submodule.

We are no longer executing a 'git submodule update --recursive'
in the patch-chromium.sh script, since init-repository.py
takes care of checking out the proper revisions.

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

On Mac we also want to clone submodules which
have an os tag 'mac'.

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

The script now also installs a gerrit git remote
and the Change-Id git hook.
Further it also resets the chromium repository
and applies the patches on top.

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

Chromium is not using a regular git submodule based
repository layout. Therefore some special tweaking is
necessary.
This script will take care of setting the correct
submodule paths and references after cloning the
qtwebengine repository.
Further it also downloads and builds the ninja build tool.

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