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
Parrot::Co
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.
[snip]
Possible ways forward:
[snip]
7) have every configure step print it's package name as part of it's
output
Ba
Patch applied to trunk in r20603. Closing ticket.
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
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
w
# New Ticket Created by James Keenan
# Please include the string: [perl #44353]
# in the subject line of all future correspondence about this issue.
# 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
---
Fl