Hi,
brian d foy wrote:
> Beyond that, is there a way for everyone to see the list of those
> modules? That's what I meant about you changing pause, much like you
> did for 06.perms.
>
> It would also be nice to see that bit set somewhere like CPAN Search,
> maybe with a button that says "I want t
Hi Ovid,
Ovid schrieb:
--- Andy Armstrong <[EMAIL PROTECTED]> wrote:
Can anyone think of anything wrong with the approach of replacing
require with an instrumented version? If the consensus is that that's
a sensible approach I'll play with tidying up the code.
You know, that solves an an
Hi Andy,
Andy Armstrong schrieb:
On 31 Jul 2007, at 12:27, David Cantrell wrote:
Wrong. If AUTHOR_TESTING then surely all tests *must* pass both with
and *without* the optional module!
I'm still stuck on thinking up a decent name for this:
http://drhyde.cvs.sourceforge.net/drhyde/perlmodules
Andy Lester schrieb:
I suspect that some of the stuff in Test::Harness, such as Straps.pm
and Point.pm, would go away. That's a bit of concern for me as I've no
way of knowing how ubiquitous their use is. I do know that a few
people are overriding straps -- 'prove' even has a switch to let you
Hi Eric,
thanks for bringing this issue to a wider audience. M::SD could *really*
use some reasonable tests.
Eric Wilhelm schrieb:
[...]
What's the best way to test this sort of thing?
I could certainly run some simple checks on core modules, but I envision
myself quickly getting into diffe
David Golden schrieb:
Maybe it would make sense to get DSLIP added to the META.yml spec instead.
Andy and Schwern made a similar point. I agree with that.
Also, I agree that the original idea perhaps wasn't great - except for
the fact that the blessing of the modules list maintainers *is* gre
Andy Lester schrieb:
On Nov 5, 2006, at 12:07 PM, Steffen Mueller wrote:
How about a mandatory or optional metric for modules registered with
the modules list? Why is that a sign of (q|kw)alit(y|ee)? Because it
means the author has the blessing of the module list maintainers as
far as the
Hi perl-qa,
there's been a lot of discussion about CPANTS metrics in the recent past.
How about a mandatory or optional metric for modules registered with the
modules list? Why is that a sign of (q|kw)alit(y|ee)? Because it means
the author has the blessing of the module list maintainers as fa
Michael G Schwern schrieb:
This doesn't really explain why test.pl is bad.
[...]
Agreed!
This distribution uses 'test.pl' for its tests. The output of 'test.pl' is not parsed. When
"make test" is run by automated installers (for example, the CPAN shell) your tests will
always appear to h
Hi,
Michael G Schwern schrieb:
So making "no_test_pl" a kwalitee test is a good idea.
So adding this to Module::CPANTS::Kwalitee::Files in the obvious place
should do exactly that. Perhaps we should call it "old_testing_scheme"
or so instead, but I'll go with your suggestion:
{
Hi again,
Michael G Schwern schrieb:
So making "no_test_pl" a kwalitee test is a good idea.
of course, adding a mention in the docs helps, too. So I should have
made it a patch. Sorry. I didn't have the svn sources.
Hence:
=item * has_test_pl
And if people decide that this should be optio
John Peacock schrieb:
David Golden wrote:
Dropping the "exists" or changing that to "ref $node->{version}" makes
it all work just fine.
I'll run a few tests in the AM, using both YAML and the fallback M::B::YAML to
make sure there aren't any other surprises...
(Though technically, it really
Andy Lester schrieb:
At this point, CPANTS rules are getting into the realm of purely
self-pleasuring. If more than a dozen people outside of this small
enclave of people cares whether a module gets a 16 or 17, I'll be shocked.
Personally, I don't. But other people seem to.
2) If you find th
Jonathan Rockway schrieb:
1) Module authors need to re-release their modules whenever
Module::Install is updated.
This is the only viable solution. Anybody using Module::Install for
their modules should be aware of that. Of course, if the changes between
the Module::Install releases don't mat
Randy W. Sims schrieb:
Steffen Mueller wrote:
Feedback is welcome, though I'd rather not talk about the way I
determine the version number. It works for all known versions of
Module::Install.
I don't think I like it. It makes me nervous for some reason... For
example, who
Hi,
Thomas Klausner schrieb:
On Tue, Jul 18, 2006 at 12:27:30PM +0200, Steffen Mueller wrote:
we had a discussion about distributions with broken versions of
Module::Install. Using Module::CPANTS::Kwalitee::* as models I wrote a
simple plugin that calculates a Kwalitee metric
Hi domm, hi perl.qa,
we had a discussion about distributions with broken versions of
Module::Install. Using Module::CPANTS::Kwalitee::* as models I wrote a
simple plugin that calculates a Kwalitee metric "uses_broken_installer".
- If the distribution doesn't use Module::Install, it's fine for
Steffen Mueller schrieb:
You
can find a complete (and somewhat current) list of problematic modules
at http://steffen-mueller.net/mi_old.html
I have just completed rerunning the script that generated that list. The
new list is available at above URL.
Steffen
Jan Dubois schrieb:
Module::Install version 0.60 and earlier pushes one of its own
directories to the front of @INC, and that directory contains Base.pm or
BASE.pm, shadowing the core base.pm on case insensitive filesystems
(Windows, OS X).
Thank you for the explanation. I wasn't aware of this.
Michael G Schwern schrieb:
On 7/6/06, Steffen Mueller <[EMAIL PROTECTED]> wrote:
Versions of Module::Install < 0.61 do not work on the current ActivePerl
release 5.8.8 build 817.
What's broken and why suddenly 5.8.8?
ActiveState introduced some new form of local configuration
David Golden schrieb:
What about adding NO_BROKEN_INSTALLER as a Kwalitee point for CPANTS?
Maybe tongue-in-cheek, but it's actually a good idea. Module::Install
pre-0.61 is certainly "broken".
What does Module::Build count as? ;)
Steffen
Hi perl.qa,
hopefully, this message will not provoke another flame war about
Module::Install and Module::Build. Please don't feel tempted. I don't
care which build system you use if it works.
Versions of Module::Install < 0.61 do not work on the current ActivePerl
release 5.8.8 build 817. Th
Adam Kennedy wrote:
HOWEVER, that requires that they NOT be using a custom extension, and
than the commands used in the Makefile.PL match those in the current
version of Module::Install.
This has caused a couple of bug reports against PAR distributions with
old/broken MI's where the person in
Matisse Enzer wrote:
#2 has it's benefits too - you could even mirror all of CPAN, and
just maintain a script with "install" commands to install the
versions you
want;
install "KWILLIAMS/Module-Build-0.27_04.tar.gz";
etc. That makes both upgrading easy and makes your build proces
Hi,
Tyler MacDonald wrote:
And now that I think about it, I'm not so convinced about that whole
"concenience for the end user" nonsense. If they're mucking about installing
perl modules from the CPAN packages by themself, they're probably developers
that need some extra time to sit there
25 matches
Mail list logo
