Re: [Zephyr-users] Introducing west, Zephyr's meta-tool
toggle quoted messageShow quoted text
From: Luiz Augusto von Dentz <firstname.lastname@example.org>
Sent: 29 January 2019 12:25
To: Cufi, Carles <Carles.Cufi@nordicsemi.no>
Cc: Jamie Mccrae <Jamie.Mccrae@lairdtech.com>; zephyr-devel <zephyr-
Subject: Re: [Zephyr-devel] [Zephyr-users] Introducing west, Zephyr's
On Tue, Jan 29, 2019 at 11:40 AM Cufi, Carles
which are described in the GitHub issue describing multi-repo:
Hi Jamie, Luiz,
-----Original Message-----There are a number of reasons why we don't use Git submodules, all of
From: Jamie Mccrae <Jamie.Mccrae@lairdtech.com>
Sent: 29 January 2019 10:35
To: Luiz Augusto von Dentz <email@example.com>; Cufi, Carles
Cc: zephyr-devel <firstname.lastname@example.org>; zephyr-
Subject: RE: [Zephyr-devel] [Zephyr-users] Introducing west,
GitHub. The plan is to adapt to what the service offers and try to
Note that we have not at any point considered moving away from
find a solution that works well with it. This is also one of the
reasons we are first introducing west without actually splitting the
ext/ folder into multiple external repos: we want to expose users to
west before we start doing more radical changes.
Well good, though Im not sure what problem does west solves then?
For pulling it sounds like submodules is the preferable solution
(to linux folks at least):
https://public-inbox.org/git/338901fc-6dc8-2684-c116-393e603f85e9@I agree with Luiz here, what does west provide that submodules
doesn't provide? Why do I and others now need yet another piece of
software to build Zephyr code (python)?
https://github.com/zephyrproject-rtos/zephyr/issues/6770Well I didn't have to go as far since someone already commented similar
So attached vs detached approach, there seems to be quite many on the
camp that we need to have the repositories attached while some
considered the detached approach a must have. As individual contributor
I think using the attached approach is a must, specially if one wants to
actually run sanity checks which sometimes is necessary e.g. when you
are actually writing a test case which depends on a feature from a
If by "attached" you mean that projects in the manifest are locked at a particular SHA, then that is exactly what we will do upstream (https://github.com/zephyrproject-rtos/zephyr/blob/master/west.yml#L37
). That is not to say that some downstreams may choose to free float on the tip of a branch, but this is *not* going to be the case for upstream Zephyr. I will edit the body of the issue to make that clear.
Join email@example.com to automatically receive all group messages.