unfortuntately I had not considered the case where a non-dirty state in the build directory could create false-positive error messages. To avoid this, we additionally check that a global install even exists, otherwise we assume we must be local install even if in a non-dirty state.