#I am asking because it doesn't seem to
rough tree
so, based on your last message I don't think i did it right.
when I am in ./a I ran dagger mod install -m ../c ../b thinking "install C and B into the module in the current folder"
opal marsh
Ahh okay, yeah it was saying "install ../b to ../c", but totally get the confusion
rough tree
let me check if ../b to ../c happened
yup!! even though I was in ../a , ../b is a dependency of ../c
I wonder if the CLI UX can be changed to be explicit. like
dagger mod install --source a --target b
opal marsh
Okay, well I guess it's at least logically consistent in behavior but I can see how the syntax is very confusing
rough tree
That would have make more sense to me
opal marsh
I wonder if the CLI UX can be changed to be explicit. like
`dagger mod install ...
Yes exactly, I think something along those lines is probably a good idea
rough tree
target could take multiple modules
opal marsh
Added a note about this to this PR for CLI polish: https://github.com/dagger/dagger/pull/6533#issuecomment-1922358536
cc @covert ember ^
Thanks for the 100th time for all the feedback on everything, it's truly incredibly helpful 🙂