-
Notifications
You must be signed in to change notification settings - Fork 127
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
Projects in the west directory are not forbidden #102
Comments
I would suggest to error out. And in future we could consider to add |
This would require adding Perhaps a |
@mbolivar you're right, it would be required for every command, expect maybe I think my main point was to suggest the error for now, and then take it up, if someone needs this. |
Erroring out seems sane. |
Fixes: zephyrproject-rtos#102 This commit introduces a list of restricted folders that are compared against project defined paths to ensure a manifest does not contain paths ending in the west folder, e.g.: - west - west/foo - foo/../west while still allowing folders, such as: - west-ext as project folder. Signed-off-by: Torsten Rasmussen <torsten.rasmussen@nordicsemi.no>
Fixes: zephyrproject-rtos#102 This commit introduces a list of restricted folders that are compared against project defined paths to ensure a manifest does not contain paths ending in the west folder, e.g.: - west - west/foo - foo/../west while still allowing folders, such as: - west-ext as project folder. Signed-off-by: Torsten Rasmussen <torsten.rasmussen@nordicsemi.no>
Migrating to enhancement |
Since this issue was filed, WEST_DIR has been renamed to hidden directory BUT I tested this again with |
Originally reported by @tejlmand.
For example, even with forbidding projects named
west
.west
ormanifest
, this manifest fragment is legal:This creates a structure where the top-level
west
directory contains a.git
for thenot-west
repository, which is very strange.Arguably this is user error but the current behavior seems undesirable. We should consider what to do here:
The text was updated successfully, but these errors were encountered: