Comment 3 for bug 1633613

The issue I see is that I, as a rather new user to snaps and snapcraft need to take action with that information.

* The error message states something which I cannot use for possible action.
* Kyle's explanation is much better, at least it goes from plain data to information.

Now, even if the message contained what Kyle said, it still requires some cumbersome research by the user to go to action, Ideally it could be more explanatory and not assume much context, questions that I find useful to craft a decent error output in this case are:

* What is the prime directory?
* Why is it looking there?
* How was this expecting the binary to end up there?
* Can I get more debug output?

The issue ended up being the "-" in front of - bin/caddy in the last line, I am being completely naive here but I presume that dash is removing the binary from the build? that is a chance for the app to be extra user friendly and connect the dots for me assuming I am a clueless person cargo-culting a block (which I am).

Since snapcraft presents us with a declarative form of expressing a package (super cool btw) I would expect that when that process fails you treat me like someone that knows nothing about what happens inside the process, just know the declaration language.