James E Keenan wrote:
But I didn't actually implement this. What I actually implemented was
specifying the configuration step name *as an alternative to* specifying
a portion of the step's description. While this satisfied particle's
original request, it led to some ugly code in
particle:
I think this patch should get verbose-step to work the way you wanted it
to. Please review. This was developed in the 'step_verbosity_by_name'
branch; the attached is a diff between trunk and that branch.
kid51
Index: lib/Parrot/Configure/Options.pm
Joshua Hoblitt wrote:
The issue is here is that there is nothing in Configure.pl's output to
correlate the package name of the step with the output seen from a
typical run.
For example, say the test that outputs Determining architecture, OS and
JIT capability... is failing
# New Ticket Created by James Keenan
# Please include the string: [perl #44353]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44353
---
osname= linux
osvers= 2.6.18.3
arch= i486-linux-gnu-thread-multi
cc= cc
The issue is here is that there is nothing in Configure.pl's output to
correlate the package name of the step with the output seen from a
typical run.
For example, say the test that outputs Determining architecture, OS and
JIT capability... is failing for some reason so you
