Nixing this, or at least delaying it. Since Testify has no C++ code, you don't need to go through the build and install cycle to work with it in dev; just add its inst directory to your path.
And for real releases, it's appropriate that the code come from the last commit that's actually in source control, not local changes. If this is done, it should be a separate dist-local target.
Nixing this, or at least delaying it. Since Testify has no C++ code, you don't need to go through the build and install cycle to work with it in dev; just add its
instdirectory to your path.And for real releases, it's appropriate that the code come from the last commit that's actually in source control, not local changes. If this is done, it should be a separate
dist-localtarget.Closing as wontfix.