Can you please stop testing with 5.9.x as this does not have any meaning as of today (or as of today 2 years ago). I'm sending this request because I got a confusing/non-sensical FAIL from an old developer version of perl:
http://www.nntp.perl.org/group/perl.cpan.testers/2009/10/msg5580343.html
Thanks,
Burak
> http://www.nntp.perl.org/group/perl.cpan.testers/2009/10/msg5580343.html
<plug>
For CPAN.pm users the following distroprefs file implements this:
match:
perlconfig:
version: '^5\.[79]'
cpanconfig:
test_report: 0
</plug>
OO,
--
andreas
> <plug>
>
> For CPAN.pm users the following distroprefs file implements this:
>
> match:
> perlconfig:
> version: '^5\.[79]'
> cpanconfig:
> test_report: 0
>
> </plug>
Nice tip thanks :) but I don't see the point of still using these junk. They are obsolete and even invalid. Sending reports with them ain't helping but spamming.
> OO,
> --
> andreas
>> For CPAN.pm users the following distroprefs file implements this:
>>
>> match:
>> perlconfig:
>> version: '^5\.[79]'
>> cpanconfig:
>> test_report: 0
>>
>> </plug>
> Nice tip thanks :) but I don't see the point of still using these
> junk. They are obsolete and even invalid. Sending reports with them
> ain't helping but spamming.
Probably a misunderstanding: the distroprefs file I suggested helps
testers to keep their test results for themselves. So if they ever test
something with a perl 5.7.x or 5.9.x then they will not send a report
about it. Just as you requested.
In the past I have been guilty myself of sending reports with old
bleadperls, that's why I came up with this protection against my own
testing euphoria.
--
andreas
Confirmed. I, for instance, have a lot of those old Perls installed
somewhere and occasionally trip into one of them when not beeing
careful or some PATHs still point to them. I will now use this
distropref.
Kind regards,
Steffen
--
Steffen Schwigon <s...@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
Deutscher Perl-Workshop <http://www.perl-workshop.de/>
There is indeed no point testing with obsolete dev versions of perl, but
you have to remember that at least the most prolific testers have things
largely automated. I'd not be at all surprised if someone forgets to
remove an old version of perl occasionally. Andreas's magic makes that
less of a problem.
Andreas - how does that interact with, eg, me having a file with
settings specific to a particular distribution? Are rules from both
files applied?
And ooh, I see that there's an archname in there too now! Yay! That'll
be very handy for excluding a particular distribution which crashes my
NetBSD tester but works just fine everywhere else.
--
David Cantrell | Minister for Arbitrary Justice
"Every normal man must be tempted at times to spit on his hands,
hoist the black flag, and begin slitting throats." -- H. L. Mencken
> There is indeed no point testing with obsolete dev versions of perl, but
> you have to remember that at least the most prolific testers have things
> largely automated. I'd not be at all surprised if someone forgets to
> remove an old version of perl occasionally. Andreas's magic makes that
> less of a problem.
> Andreas - how does that interact with, eg, me having a file with
> settings specific to a particular distribution? Are rules from both
> files applied?
Glad you asked. Nope, sorry, the distroprefs mechanism only applies the first match.
Files are processed in alphabetical order. I have:
-rw-rw-r-- 1 k k 11917 17. Aug 08:44 01.DISABLED.yml
-rw-rw-r-- 1 k k 1167 17. Aug 08:44 02.NOREPORT.yml
and after these two "normal" distroprefs files.
> And ooh, I see that there's an archname in there too now! Yay! That'll
> be very handy for excluding a particular distribution which crashes my
> NetBSD tester but works just fine everywhere else.
Glad you like it, glad you found it:)
--
andreas
andreas.koe...@franz.ak.mind.de (Andreas J. Koenig) writes:
> Glad you asked. Nope, sorry, the distroprefs mechanism only applies
> the first match. Files are processed in alphabetical order. I have:
>
> -rw-rw-r-- 1 k k 11917 17. Aug 08:44 01.DISABLED.yml
> -rw-rw-r-- 1 k k 1167 17. Aug 08:44 02.NOREPORT.yml
>
> and after these two "normal" distroprefs files.
Nice spin-off about the cool distroprefs feature.
My follow-up question:
Your personal "example" distroprefs files (which I often use
regardless of the warning :-)) are contained in the CPAN.pm
distribution but not installed.
Can you arrange that they are more easily visible and accessible,
e.g. as own sub-distribution?
I always copy them from the temporary .cpan/build/ dir but maybe you
could explicitely bundle them so one could install them with "install
CPAN::DistroPrefs" and "o conf prefs_dir" to some
"site_perl/auto/CPAN/DistroPrefs/", or even auto_configure CPAN.pm to
it when installed.(*)
(*) Sometimes I believe I once even used remote URLs to distroprefs
pointing to cpan.org but I can't remember. Can I?
Anyway, just an idea, not a real request, I know your TODO list is
full. :-)
Thanks for distro prefs, thanks for CPAN.pm.
>> -----Original Message-----
>> From: Andreas J. Koenig
>> [mailto:andreas.koe...@franz.ak.mind.de]
>> Sent: Saturday, October 17, 2009 6:56 AM
>> To: Burak Gürsoy
>> Cc: cpan-teste...@perl.org; cpan.dcoll...@gmail.com
>> Subject: Re: Please do not test with obsolete bleads
>>
>
>> <plug>
>>
>> For CPAN.pm users the following distroprefs file implements this:
>>
>> match:
>> perlconfig:
>> version: '^5\.[79]'
>> cpanconfig:
>> test_report: 0
>>
>> </plug>
>
> Nice tip thanks :) but I don't see the point of still using these
> junk. They are obsolete and even invalid.
Testing old perls is very useful to find regressions in perl itself
(keywords: binary search, or git bisect).
> Sending reports with them ain't helping but spamming.
But this is true.
Regards,
Slaven
--
Slaven Rezic - slaven <at> rezic <dot> de
BBBike - route planner for cyclists in Berlin
WWW version: http://www.bbbike.de
Perl/Tk version for Unix and Windows: http://bbbike.sourceforge.net
> My follow-up question:
> Your personal "example" distroprefs files (which I often use
> regardless of the warning :-)) are contained in the CPAN.pm
> distribution but not installed.
> Can you arrange that they are more easily visible and accessible,
> e.g. as own sub-distribution?
> I always copy them from the temporary .cpan/build/ dir but maybe you
> could explicitely bundle them so one could install them with "install
> CPAN::DistroPrefs" and "o conf prefs_dir" to some
> "site_perl/auto/CPAN/DistroPrefs/", or even auto_configure CPAN.pm to
> it when installed.(*)
> (*) Sometimes I believe I once even used remote URLs to distroprefs
> pointing to cpan.org but I can't remember. Can I?
> Anyway, just an idea, not a real request, I know your TODO list is
> full. :-)
For those who really want to follow my distroprefs the simplest solution
(I think) is to make ~/.cpan/prefs a symlink to the working copy of the
git repository of CPAN.pm. Then from time to time a 'git pull', maybe
done by cron.
Ideas to make the distribution of distroprefs more service-like have
popped up from time to time but so far nothing has gained sufficient
attention. But now that I've said that I have a very nice idea indeed.
I'll give it a reality check in the next days and let you know...
--
andreas