>>>>> On Fri, 27 Nov 2009 09:28:28 +0100, Oliver Paukstadt
>>>>> <[email protected]> said:
>> Imagine a bughunter is trying out variations in the C compiler or in the
>> toolchain or in installed versions of modules required or is bisecting
>> perl. Then it would be wonderful to see the resulting variations in
>> cpantesters. Currently the bughunter has to wipe out the one line in the
>> reports-sent database to deliver more than one PASS or FAIL.
>>
> What about
> sh Configure -Darchname='bisect-b3dc64032ba370e494dd752a46f2a53d'
> for a different perl?
Acme::BadExample:) How many parts of the cpantesters ecology would break
this? Imagine a cpan testers matrix with these crap labels:)
> This should generate a different archname which is registered in
> reports-sent.db. This would help at least for all new compiled
> perls, not for the mentioned module version variations.
> Quick hack solution for this might be: Change printed archname in
> reports-sent.db to
> $Config{archname}."-".$ENV{'CPAN_Reporter_Tag'} if defined.
OK, something like this might work, it has no impact on the rest of the
world.
--
andreas
