@@ -92,12 +92,15 @@ recipes may reference each other freely. The only restriction is that a
9292particular recipe or class must only be defined by one layer. It is not allowed
9393to "overwrite" a recipe in a layer above.
9494
95- Layers must be configured in ``config.yaml `` to be picked up. This is just a
96- simple list of layer names that are then expected in the ``layers `` directory::
95+ Layers must be configured in ``config.yaml `` to be picked up. This is a list of
96+ either simple layer names that are then expected in the ``layers `` directory or
97+ an SCM specification where the layer is fetched from::
9798
9899 layers:
99100 - myapp
100- - bsp
101+ - name: bsp
102+ scm: git
103+ url: git@github.com:...
101104
102105The order of layers is important with respect to settings made by
103106``default.yaml `` in the various layers. The project root has the highest
@@ -1927,10 +1930,10 @@ equal.
19271930layers
19281931~~~~~~
19291932
1930- Type: List of strings or SCM-Dictionary or List of SCM- Dictionaries
1933+ Type: List of strings or SCM-Dictionaries
19311934
19321935The ``layers `` section consists of a list of layer names that are then expected
1933- in the ``layers `` directory relative to the `` conig.yaml `` referencing them ::
1936+ in the ``layers `` directory of the project root directory ::
19341937
19351938 layers:
19361939 - myapp
@@ -1949,9 +1952,10 @@ of lower precedence.
19491952
19501953See :ref: `configuration ` for more information.
19511954
1952- Typically layers have their own VCS. To provide them to the root-recipes common
1953- VCS-methods like git-submodules can be used. Another possibility is to provide a
1954- SCM-Dictionary (see :ref: `configuration-recipes-scm `)::
1955+ Typically, layers are stored in their own SCM. To provide them to the root
1956+ recipes, common SCM-methods like git-submodules can be used. Another
1957+ possibility is to provide an SCM-Dictionary (see
1958+ :ref: `configuration-recipes-scm `) and let Bob manage the layer::
19551959
19561960 layers:
19571961 - name: myapp
@@ -1960,17 +1964,17 @@ SCM-Dictionary (see :ref:`configuration-recipes-scm`)::
19601964 commit: ...
19611965 - bsp
19621966
1963- Only `git `,`svn`,`url` and `cvs ` scm's are supported for layers. During layers
1964- checkout the regular ``whitelist `` and ``scmOverrides `` settings are not used.
1965- Instead the checkout could be controlled by ``layersWhitelist `` and
1966- ``layersScmOverrides ``.
1967-
1968- If a scmSpec is given Bob takes care of the layer management:
1967+ If a layer SCM specification is given, Bob takes care of the layer management:
19691968
1970- - layers are checked out / updated during bob-build (except build-only)
1971- - bob layers command to update / show status (see :ref: `manpage-layers `).
1969+ - Layers are checked out / updated during bob-build (except build-only).
1970+ - The ``bob layers `` command can update layers or show their status (see
1971+ :ref: `manpage-layers `).
19721972
1973- .. _configuration-config-plugins :
1973+ Only git, svn, url and cvs SCMs are supported for layers. Because layers are
1974+ fetched and updated before any :ref: `configuration-config-usr ` is parsed, the
1975+ regular ``whitelist `` and ``scmOverrides `` settings are not used. Instead,
1976+ layer checkouts are controlled by ``layersWhitelist `` and
1977+ ``layersScmOverrides ``.
19741978
19751979layersWhitelist
19761980~~~~~~~~~~~~~~~
@@ -1983,6 +1987,8 @@ layersScmOverrides
19831987:ref: `configuration-config-scmOverrides ` used by layers checkout / update.
19841988Conditional overrides are not supported.
19851989
1990+ .. _configuration-config-plugins :
1991+
19861992plugins
19871993~~~~~~~
19881994
0 commit comments