west init gives wrong config path for a manifest file in nested directories #774
Description
when initializing my workspace, i want the manifest file to be located two levels below the west top dir, in orb/private
.
├── .west
├── bootloader
│ └── mcuboot
├── modules
│ ├── ...
├── orb
│ ├── private
│ └── public
└── zephyr
When initializing with cd orb && west init -l --mf private/west.yml ., the west config created is:
[manifest]
path = orb
file = private/west.yml
but then zephyr_module.py from Zephyr 4.0 fails because the manifest isn't in orb but orb/private.
If I modify .west/config manually, to have path = orb/private, then it works.
Would it be possible to have the path points to the manifest directory, and file only take the name of the west file?