Closed mneumann closed 1 year ago
savi build spec
works when I manually git clone
the missing deps.
If you run savi deps update --for spec
it will fetch the dependencies for the spec
manifest.
If you don't include --for
then Savi will try to guess which one is the manifest that you want (if you have exactly one bin
it will guess that, but otherwise it will guess the lib
if there is exactly one of those).
You can tell Savi that your spec
manifest is the "main" binary to use as the default if you declare it as :manifest main spec
as :manifest bin spec
. This will make it so that it is always selected by default if you don't include a --for MANIFEST_NAME
CLI argument.
This is all under-documented at the moment, so it's not surprising that you didn't know this. I definitely need to spend some time writing clear documentation for the packaging and manifests system in general.
I'd make savi deps update
fetch all dependencies, and only if you specify --for
then fetch only those.
That seems reasonable. I'll update the ticket title.
I have this
manifest.savi
:Running
savi deps update
gives me:When I run
savi build spec
, I get the following errors: