Lines Matching full:example
22 history, looks like the following figure (though some parts of this example are
120 For example:
128 url-base: https://git.example.com/base1
130 url-base: https://git.example.com/base2
149 bases are respectively ``https://git.example.com/base1`` and
150 ``https://git.example.com/base2``. You can use SSH URL bases as well; for
151 example, you might use ``git@example.com:base1`` if ``remote1`` supported Git
166 Here is an example. We'll assume the ``remotes`` given above.
168 .. Note: if you change this example, keep the equivalent manifest below in
177 description: the first example project
182 A multi-line description of the second example
194 ``https://git.example.com/base1/proj1``. The remote ``url-base`` is appended
206 ``https://git.example.com/base2/my-path``. The ``repo-path`` attribute, if
336 url-base: https://git.example.com/base1
338 url-base: https://git.example.com/base2
342 description: the first example project
347 A multi-line description of the second example
377 As an example, let's consider this snippet from the zephyr repository's
409 repository URL will be used by default. For example, if the URL is
410 ``https://git.example.com/project-repo``, the manifest repository would
432 Here is an example:
509 change the list of valid ``version`` values. For example, ``version:
535 example, ``west update`` will not update inactive projects, and ``west list``
536 will not print information about them by default. As another example, any
563 For example, this lets you run a ``west forall`` command only on the projects
593 For example, in this manifest fragment:
617 contain these characters elsewhere in their names. For example, ``foo-bar`` and
636 To enable a group, prefix its name with a plus sign (+). For example,
648 To disable a group, prefix its name with a dash (-). For example, ``groupA``
675 group, add its name prefixed with ``-``. For example, setting
689 This section contains example situations involving project groups and active
701 Example 1: no disabled groups
720 remote: example-remote
722 - name: example-remote
723 url-base: https://git.example.com
732 Example 2: Disabling one group via manifest
752 remote: example-remote
754 - name: example-remote
755 url-base: https://git.example.com
763 Example 3: Disabling multiple groups via manifest
783 remote: example-remote
785 - name: example-remote
786 url-base: https://git.example.com
794 Example 4: Disabling a group via configuration
812 remote: example-remote
814 - name: example-remote
815 url-base: https://git.example.com
826 Example 5: Overriding a disabled group via configuration
847 remote: example-remote
849 - name: example-remote
850 url-base: https://git.example.com
861 Example 6: Overriding multiple disabled groups via configuration
882 remote: example-remote
884 - name: example-remote
885 url-base: https://git.example.com
896 Example 7: Disabling multiple groups via configuration
915 remote: example-remote
917 - name: example-remote
918 url-base: https://git.example.com
953 Example 1: no overrides
964 url: https://git.example.com/child
967 url: https://git.example.com/project-1
980 url: https://git.example.com/project-2
982 url: https://git.example.com/project-3
995 Example 2: overriding an imported ``group-filter`` via manifest
1007 url: https://git.example.com/child
1010 url: https://git.example.com/project-1
1023 url: https://git.example.com/project-2
1027 url: https://git.example.com/project-3
1043 Example 3: overriding an imported ``group-filter`` via configuration
1054 url: https://git.example.com/child
1057 url: https://git.example.com/project-1
1070 url: https://git.example.com/project-2
1074 url: https://git.example.com/project-3
1126 For example, let's say you have a source code repository ``foo``, which has
1158 For example, let's say you have a source code repository ``foo``, which has
1196 Example manifest fragment:
1211 Example Python usage:
1253 other files. For example, a project named ``foo`` in your :file:`west.yml`
1296 ``false`` or missing, it has no effect. For example, this manifest would import
1323 Example 1.1: Downstream of a Zephyr release
1362 ``my-repo`` is hosted at ``https://git.example.com/my-repo``:
1366 west init -m https://git.example.com/my-repo my-downstream
1381 Example 1.2: "Rolling release" Zephyr downstream
1404 west init -m https://git.example.com/my-repo my-downstream
1425 repository's working tree. See :ref:`west-manifest-ex2.2` for an example.
1429 Example 1.3: Downstream of a Zephyr release, with module fork
1446 url-base: https://git.example.com
1472 - is cloned from ``https://git.example.com/hal_nordic`` instead of
1503 Here is an example:
1534 Example 2.1: Downstream of a Zephyr release with explicit path
1553 the ``zephyr`` project. This example is contrived, but shows the idea.
1560 Example 2.2: Downstream with directory of manifest files
1608 The :file:`.yml` file names are prefixed with numbers in this example to
1620 precedence. For example, if :file:`01-libraries.yml` defines ``hal_nordic``,
1625 as we'll see in the next example.
1629 Example 2.3: Continuous Integration overrides
1688 Allowlists override blocklists if both are given. For example, if a project is
1693 Example 3.1: Downstream with name allowlist
1699 hosted at ``https://git.example.com/mainline/manifest``.
1708 url: https://git.example.com/mainline/app
1711 url: https://git.example.com/mainline/lib
1714 url: https://git.example.com/mainline/lib2
1720 url: https://git.example.com/mainline/manifest
1726 url: https://git.example.com/downstream/app
1729 url: https://git.example.com/downstream/lib3
1738 url: https://git.example.com/mainline/manifest
1740 url: https://git.example.com/downstream/app
1743 url: https://git.example.com/downstream/lib3
1746 url: https://git.example.com/mainline/app
1749 url: https://git.example.com/mainline/lib2
1756 Example 3.2: Downstream with path allowlist
1759 Here is an example showing how to allowlist mainline's libraries only,
1769 url: https://git.example.com/mainline/app
1772 url: https://git.example.com/mainline/lib
1775 url: https://git.example.com/mainline/lib2
1781 url: https://git.example.com/mainline/manifest
1785 url: https://git.example.com/downstream/app
1788 url: https://git.example.com/downstream/lib3
1798 url: https://git.example.com/mainline/lib
1801 url: https://git.example.com/mainline/lib2
1803 url: https://git.example.com/mainline/manifest
1805 url: https://git.example.com/downstream/app
1808 url: https://git.example.com/downstream/lib3
1812 Example 3.3: Downstream with path blocklist
1815 Here's an example showing how to block all vendor HALs from mainline by
1827 url-base: https://git.example.com/mainline
1845 url: https://git.example.com/mainline/manifest
1850 url: https://git.example.com/downstream/hal_foo
1861 url-base: https://git.example.com/mainline
1869 repo-path: https://git.example.com/mainline/manifest
1872 url: https://git.example.com/downstream/hal_foo
1876 Example 3.4: Import into a subdirectory
1882 For example, suppose you want to import this manifest from project ``foo``,
1890 remote: example
1892 - name: example
1893 url-base: https://git.example.com
1916 url: https://git.example.com/foo
1927 remote: example
1929 - name: example
1930 url-base: https://git.example.com
1949 Example 4.1: Downstream with sequence of manifest files
1952 This example manifest is equivalent to the manifest in
1971 Example 4.2: Import order illustration
1974 This more complicated example shows the order that west imports manifest files:
1996 For this example, west resolves imports in this order:
2086 example, if ``import-1`` contains a project named ``bar``, that is ignored,
2099 ``P`` itself. For example, this means ``west update P`` would update
2155 For example, in ``[-foo] + [+foo]``, group ``foo`` is *enabled*.
2159 elements which are redundant using these rules. For example, ``[+foo] +
2161 above. As another example, ``[-foo] + [+foo]`` could be written as the empty