Application developers will download pre-complied images from the Enea Portal or will receive prebuilt images from the platform developers. For further information on this see Enea Linux Application Development Guide.

The source for this Enea Linux release is available for cloning from a set of Git repositories. To manage the different repositories, Google's repo tool is used. The basic idea is to store a list with (repo-URL, version) tuples in a separate file, known as the manifest. The repo tool is then used to traverse the list and clone the specified versions of the repositories. See https://code.google.com/p/git-repo/ for more info. To use repo tool to download the source for Enea Linux, follow the steps below: Make sure that the repo tool is installed. If not, follow the instructions below: $ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+x ~/bin/repoThe instruction assumes that ~/bin exists and is included in the PATH variable. Use the repo tool to download the source:FIXME: At final release the tag for the manifest must be set in mainfest_conf.mk as MANIFESTHASH, typically something like refs/tags/EL6. Before final release, it is possible to set MANIFESTHASH on the make command line to override the value, e.g. with a commit hash string for a release candidate to be tested $ mkdir enea-linux $ cd enea-linux $ repo init -u \ -b \ -m <manifest file> $ repo sync The parameter <manifest file> depends on the target. Use the following: The source code is now downloaded. Current directory will contain a README file with instructions on how to build the distro and boot the target. For convenience, these instructions are also copied into this document. See . It is not necessary to explicitly clone the manifest repository since that is done automatically by the repo tool. To see the current manifest, e.g. to get a list of the repositories, use the following command: $ repo manifest The UG should be updated with instructions on how to add customisations. That section should also contain some more info about the manifest: The manifest templates, using a branch instead of the tag EL6, ... When this is done a reference from here should be added.