question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Should "west init" run "west clone"?

See original GitHub issue

Right now, installing multi-repo Zephyr takes the following steps:

$ pip install west
$ west init <west-workspace>
$ cd <west-workspace>
$ west fetch

This issue tracks whether “west init” should run “west fetch” as well after cloning west and the manifest, to eliminate the last step before a complete installation is cloned.

I am ambivalent about this idea (generally speaking I don’t like to add features to the bootstrapper) but thought it was worth recording the question (and its resolution along with rationale).

Reasons for:

  • one less step during installation

Reasons against:

  • adds a feature to the bootstrapper which is not necessary
  • users might want to fetch with different options than can be passed to init, e.g. to fetch a subset of available projects
  • fetch might require different credentials than init, which might not be available at init time

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
tejlmandcommented, Jan 28, 2019

I think we should keep west init and west update seperate.

Reason: It allows users to do west init and then actually adjust west.yml to their needs if they wish so, before running west update

If users wants a one step approach, they can do: west init; west update or west init && west update depending on their platform.

0reactions
mbolivarcommented, Jan 29, 2019

Alright, I’m going to close this again since we all seem to agree, or at least nobody disagrees out loud 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Basics - Zephyr Project Documentation
This command creates a west workspace. ... West doesn't change your manifest repository contents after west init is run. Use ordinary Git commands ......
Read more >
Built-in commands — Zephyr Project Documentation
west init . This command creates a west workspace. It can be used in two ways: Cloning a new manifest repository from a...
Read more >
west - PyPI
west update clones the other repositories named in the manifest file, ... After running west init, you can run them from anywhere under...
Read more >
Build SOF with Zephyr — SOF Project 2.2 documentation
Running this command will: Initialize west to the ./sof/west.yml manifest if it is not already initialized. Clone and check out projects to ...
Read more >
`west` Zephyr extensions 'build' and 'flash' not found in ...
As I understand, west init initializes a cloned project as a west workspace. Therefore I am calling west build ... inside a valid...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found