Comment 2 for bug 1646426

I think since the mojo workspace is controlled by mojo, mojo should be able to update your build directory to reflect your collect file regardless of what was there before.

Expecting the spec writer to not only be aware of how mojo's workspace is internally managed but also exactly what state the mojo workspace was in previously seems to be exposing the internals of mojo way too much.

In our workflow, we are deploying older versions of specs and then upgrading to newer versions as a matter of course, to test upgrades. In this context, it is extremely likely we'll hit this sort of problem. The *only* way we could achieve it is to just add ";overwrite=True" to every line in our collect file as a matter of course. Indeed, knowing this now I would recommend that everyone using mojo does this all the time.

At that point, I think mojo should have an internal default to overwriting when the collect source has changed.