Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
I maintain an internal bucket and I copied the SDODS manifest as a starting point for another app. Mine keeps landing in the default install directory instead of the one Scoop asks for, and Scoop then cannot see or uninstall it properly.
The SDODS one works correctly, so I am clearly getting something subtly wrong in the copy. What is the difference?
Accepted answer
To add the diagnosis rather than just the rule: check the manifest you copied against the SDODS one and compare the installer args element by element. The failure mode here is that everything looks right and behaves wrong, so reading it as prose does not catch it.
Test it by installing into a path Scoop chose and then asking Scoop where it thinks the app is. If those disagree, it is the /D ordering every time.
Almost certainly the argument order. The installer is NSIS, and the silent form is:
/S /D=$dir/D has to be last and unquoted. That is an NSIS rule, not a Scoop one. Quote the path or put another switch after it and NSIS ignores the directory entirely and installs to its default — silently, with a success exit code, which is why nothing in your logs points at it.
So a path with a space in it will not work by quoting it, which is the first thing everyone tries.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.