Lines Matching +full:always +full:- +full:on

1 .. _west-history:
9 * The ability to provide an extensible and user-friendly command-line interface
12 During the development of west, a set of :ref:`west-design-constraints` were
32 * **R4**: Support both continuous tracking and commit-based (bisectable) project
40 `Git Submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ and
41 Google's `repo <https://gerrit.googlesource.com/git-repo/>`_.
49   - Does not cleanly support using zephyr as the manifest repository (**R4**)
50   - Python 2 only
51   - Does not play well with Windows
52   - Assumes Gerrit is used for code review
56   - Does not fully support **R1**, since the externally maintained repositories
58   - Does not support **R3**, since downstream copies would need to either
60   - Does not support continuous tracking of the latest ``HEAD`` in external
62   - Requires hardcoding of the paths/locations of the external repositories
80 * Out-of-tree development based on subsets of the supported boards and SoCs
82 See :ref:`west-basics` for information on how west workspaces manage multiple
85 .. _west-design-constraints:
92 - **Optional**: it is always *possible* to drop back to "raw"
93   command-line tools, i.e. use Zephyr without using west (although west itself
95   always be *convenient* to do so, however. (If all of west's features
99 - **Compatible with CMake**: building, flashing and debugging, and
100   emulator support will always remain compatible with direct use of
103 - **Cross-platform**: West is written in Python 3, and works on all
106 - **Usable as a Library**: whenever possible, west features are
112 - **Conservative about features**: no features will be accepted without
115 - **Clearly specified**: West's behavior in cases where it wraps other
118   can always find out what is happening "under the hood" when using west.