-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] west update --if-present (better name wanted) #519
Comments
From @mbolivar-nordic in #518
I will look into that but I suspect a |
Thanks for filing a feature. I'd like to start to clarify some behavior around imports. Here are a few simple cases.
What does
|
Yes I agree with 1. 2. and 3. In other words Except in case 3. where |
OK, thanks. Sketching out an implementation then, as prep work we would need:
Then
Plus any other unanticipated changes I can't think of yet. Think you can take a crack at it? |
Additionally, I think |
Hm, on second thought, we might be able to get away with just using the existing |
Why not a simple: and if those are set, then a clean This also follows how if they temporary wants to update a specific project and not wanting to add it to the list. |
It's more tedious and less dynamic to hardcode the list of projects of interest. It's simpler to dynamically If this feature is ever available I will turn it on at the global user level, not just per workspace. If there were no backward compatibility concern I would even argue it should be the default (it is the default for submodules and maybe others). In fact #518 is a bit of a mitigation for this (not just) |
From a digression in #518.
To please everyone and provide a good "out of the box" experience, west manifests can have many repos that are unnecessary to most users. As a random example, out of the 45-ish projects currently in https://github.com/zephyrproject-rtos/zephyr/blob/main/west.yml I need only 2 right now. So to save disk, network and time I never ever ran
west update
and never downloaded more than these 2 repos. Instead I alwayswest update proj1 proj2
. This also makeswest status
much shorter and readable (similar to #518, which solves a different problem).west update proj1 proj2
works but it is inconvenient. First because you have to remember to never ever runwest update
, then because the real command is actuallywest update dir1/dir2/what_was_that_name_again?
So it would be nice to have to runwest update dir1/dir2/what_was_that_name_again?
only the first time and then run justwest update --if-present
. Even better: haveif-present
in west config and then justwest update
.The text was updated successfully, but these errors were encountered: