We have the following repo structure:
\
├── src
│ ├── .paket
│ │ ├── paket.bootstrapper.exe
│ │ ├── paket.targets
│ │ ├── paket.exe
│ ├── paket.dependecies
│ ├── paket.lock
├── readme.md
├── build.fsx
├── other files
This worked well in V2. Now with V3 we get build errors that paket.dependencies file is not found and I need to ensure it is in the repo root. Indeed, when I move it there along with paket.lock, the error disappears. But this essentially means I have .paket under the src, however my dependencies and lock files are moved to the repo root despite there is no guarantee there is only one solution in this repo and they will get in conflict.
What was the reason behind the decision to have the dependencies and lock files in the repo root instead of a solution root?
We have the following repo structure:
This worked well in V2. Now with V3 we get build errors that
paket.dependenciesfile is not found and I need to ensure it is in the repo root. Indeed, when I move it there along withpaket.lock, the error disappears. But this essentially means I have.paketunder thesrc, however my dependencies and lock files are moved to the repo root despite there is no guarantee there is only one solution in this repo and they will get in conflict.What was the reason behind the decision to have the dependencies and lock files in the repo root instead of a solution root?