On 21 March 2017 at 08:02, Doug Bell <madcity...@gmail.com> wrote: > * "X" is the main type > * PASS = 1 > * FAIL = 2 > * NA = 3 > * UNKNOWN = 4 > * "Y" is the step of the process we made it to > * 0 is "complete/unknown" > * 1 is "extract" > * 2 is "build" > * 3 is "test" > * 4 is "install" > * "Z" is a step-specific status code > * "0" is always "generic/unknown" > * But for the "build" step > * 1 can mean "OS unsupported" > * 2 can mean "Compiler needed" > * 3 can mean "Dependencies failed" > > This might be over-engineering
I get the impression there might be scope for >1 value of Y and Z in a response. For instance, the flow assumes each stage blocks the next .... However, as far as assumptions go, we also assume that people won't run tests if dependencies are missing, and that assumption is proving to be wrong. So for instance, what if: 1. Configure fails, but then the user interactively fixes it and continues 2. Test fails, but the user installs anyway 3. Install fails All these 3 things could happen in the scope of a single report. </overengineering> -- Kent KENTNL - https://metacpan.org/author/KENTNL
