If a user installs the current version of a collection again, I expect a notice that it is already installed, but not reported as either a warning or error, as the final state is successful and this mirrors other package utilities.
If a user tries to install a different version, without any other flags, and the installation refuses to install the newly requested version replacing the previous installation, I would expect to see an ERROR, not a WARNING, because the request is ultimately not satisfied. (Warnings should be reserved for requests that are completed, but which may in other cases fail, such as deprecation warnings). I also expect the process to result in a non-zero return code to indicate the error to scripts that might be invoking mazer install.
Bug Report
MAZER VERSION
CONFIGURATION
DEFAULTS
SUMMARY
Failed installations, due to pre-existing installs of a different version, do not report the failure either in the output or process return code.
STEPS TO REPRODUCE
EXPECTED RESULTS
If a user installs the current version of a collection again, I expect a notice that it is already installed, but not reported as either a warning or error, as the final state is successful and this mirrors other package utilities.
If a user tries to install a different version, without any other flags, and the installation refuses to install the newly requested version replacing the previous installation, I would expect to see an ERROR, not a WARNING, because the request is ultimately not satisfied. (Warnings should be reserved for requests that are completed, but which may in other cases fail, such as deprecation warnings). I also expect the process to result in a non-zero return code to indicate the error to scripts that might be invoking
mazer install
.ACTUAL RESULTS