Re: CPANTS: has_license ?
On Mon, 19 Sep 2005 11:33:07 +0200, David Landgren [EMAIL PROTECTED] wrote: Gábor Szabó wrote: What do you think about adding a has_license kwalitee to CPANTS ? Checking if the META.yml has that entry ? This will penalise all the modules that use ExtUtils::MakeMaker, which, last time I looked, does not generate the license metadata, even though the module may clearly state the license used in the documentation. Modules that use(d) EU::MM will/should have a /^=head\d\s+(li[cs]en[cs]e|copyrights?)\b/i section in /^(readme|license)(\.txt)?$/i and/or This::Module.pm =head1 COPYRIGHT AND LICENSE In above pattern I allowed swapping the c and s because I've seen that too often to ignore. Probably by non-native English speakers I made a half-hearted attempt at patching EU::MM to provide a LICENSE key to WriteMakefile but then Real Life intervened. It did help me get an appreciation of what a thankless job the maintenance of EU::MM is, though. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using Perl 5.6.2, 5.8.0, 5.8.5, 5.9.2 on HP-UX 10.20, 11.00 11.11, AIX 4.3 5.2, SuSE 9.2 9.3, and Cygwin. http://www.cmve.net/~merijn Smoking perl: http://www.test-smoke.org,perl QA: http://qa.perl.org reports to: [EMAIL PROTECTED],perl-qa@perl.org
Re: ENV problems with testing
Michael G Schwern wrote: On Mon, Sep 19, 2005 at 09:42:52PM -0400, James E Keenan wrote: Schwern: Do you think it's worthwhile accounting for this MakeMaker anachronism in writing test files, i.e., providing an absolute path to every chdir call? I think you misunderstand. The problem is not using relative paths in chdir. The problem is that @INC contains a relative path. So if you change directories, the ./blib/lib entry in @INC is no longer valid. I see. Thanks.
Re: ENV problems with testing
On Mon, Sep 19, 2005 at 09:42:52PM -0400, James E Keenan wrote: (Secondary reason for tests needing 5.6: as you, Schwern, pointed out several weeks back, doing without qr// is just too painful!) 5.005 introduced qr// $ ~/Reference/5.005_04/bin/perl5.00504-32 -le '$r = qr/(p...)/; $^X =~ $r; print $1' perl Nicholas Clark
Re: ENV problems with testing
On Tue, Sep 20, 2005 at 02:52:53PM +0100, Nicholas Clark wrote: On Mon, Sep 19, 2005 at 09:42:52PM -0400, James E Keenan wrote: (Secondary reason for tests needing 5.6: as you, Schwern, pointed out several weeks back, doing without qr// is just too painful!) 5.005 introduced qr// $ ~/Reference/5.005_04/bin/perl5.00504-32 -le '$r = qr/(p...)/; $^X =~ $r; print $1' perl If you're using it for any serious amount of nesting (ie. building up a regex with a bunch of qr's) it didn't really stabilize until 5.6. I recall this from Email::Find and URI::Find. But for normal use its ok in 5.5. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ROCKS FALL! EVERYONE DIES! http://www.somethingpositive.net/sp05032002.shtml
Re: ENV problems with testing
On Tue, Sep 20, 2005 at 07:50:03AM -0400, James E Keenan wrote: I think you misunderstand. The problem is not using relative paths in chdir. The problem is that @INC contains a relative path. So if you change directories, the ./blib/lib entry in @INC is no longer valid. I forgot to give a solution. Basically, either require every module before chdir'ing, or run @INC through File::Spec-rel2abs(). -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Life is like a sewer - what you get out of it depends on what you put into it. - Tom Lehrer
Re: ENV problems with testing
--- Michael G Schwern [EMAIL PROTECTED] wrote:
5.005 introduced qr//
$ ~/Reference/5.005_04/bin/perl5.00504-32 -le '$r = qr/(p...)/; $^X
=~ $r; print $1'
perl
If you're using it for any serious amount of nesting (ie. building up
a regex
with a bunch of qr's) it didn't really stabilize until 5.6. I recall
this
from Email::Find and URI::Find. But for normal use its ok in 5.5.
FYI: Deeply nesting qr// constructs can have performance impacts.
ovid $ perl -le '$x=qr{x};$y = qr{y$x};print qr{$y};'
(?-xism:y(?-xism:x))
Perl will decompile the individual regexes back to strings and later
recompile them. This recompilation can produce less efficient regexes
than what you wrote. A better solution, if this turns out to impact
one's code, is to use the q{} and qq{} operators and nest them, though
when you use qq{} you'll have to remember to properly escape things.
Also, you'll want (?:) constructs in your code.
bin $ perl -le '$x=q{(?:x)};$y = q{(?:y$x)};print qr{$y};'
(?-xism:(?:y$x))
See Perl Best Practices Constructing Regexes (page 261) for more
information.
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
Re: Plugging CPANTS
Hi!
On Sun, Sep 18, 2005 at 08:18:17PM -0500, Andy Lester wrote:
Can someone please write up a paragraph and a link that I can put up
on qa.perl.org's front page?
Took me a bit longer than planned, but renovating our new appartment sucks
up a lot of time...
Anyway, I rewrote some of the pages on cpants.perl.org and I think that this
is a reasonable introduction for qa.perl.org:
-- start --
CPANTS is an acronym for CPAN Testing Service. The goals of the CPANTS
project are to provide some sort of quality measure (called Kwalitee) and
lots of metadata for all distributions on CPAN.
Please take all the information presented here with a grain of salt. The
methods used to test the distributions are a bit flakey, and some of the
Kwalitee indicators are still subjects of discussions (which should happen
on the perl-qa list).
-- end --
Enhancements by people who actually /can/ speak/write proper English are
highly anticipated.
--
#!/usr/bin/perl http://domm.zsi.at
for(ref bless{},just'another'perl'hacker){s-:+-$-gprint$_.$/}
Re: Plugging CPANTS
Thomas Klausner writes: CPANTS is an acronym for CPAN Testing Service. That would be better simplified to: CPANTS is the CPAN Testing Service. -- cos it's pretty obvious where the name comes from, and its being an acronym is hardly the most important thing about it. But if you really want to talk about it being an acronym, it should be: CPANTS is an acronym for CPAN Testing Service. -- cos there you're talking about the words rather than about the entities. Smylers -- May God bless us with enough foolishness to believe that we can make a difference in this world, so that we can do what others claim cannot be done.
