# New Ticket Created by James Keenan # Please include the string: [perl #45525] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=45525 >
A number of Parrot developers working on configuration steps (config/ */*.pm and config/*/*/*.pm) have indicated that they would benefit from better feedback when an individual configuration step fails. Since Configure.pl has for some time acted primarily as a harness for running a series of configuration steps, its objective has been to keep on going when an individual step fails. For the purpose of this RT, it is assumed that this is a good thing most of the time. But we need to make allowances for the Parrot developer who, needing to get to work quickly on a failing configuration step, wants the configuration process to come to a clean, complete halt when a particular step fails. Ideally, the user should be able to specify whether any of an indefinite number of configuration steps should have the property of being able to halt configuration as a whole upon failure. For that degree of flexibility we will probably have to evolve to a file-based configuration system as suggested by Jerry Gay in https://rt.perl.org/ rt3/Ticket/Display.html?id=44315. In the meantime, however, we can provide users with an --abort-step option to Configure.pl. This would work in a manner analogous to the current --verbose-step option, i.e., the user gets to name one and only one step whose failure causes Configure.pl to terminate with extreme prejudice. That naming would be done by configuration step number, formal name (e.g., inter::progs) or pattern match on the step's $description. Assignment: Provide an --abort-step option to Configure.pl. kid51
