On Feb 24, 2006, at 11:42 PM, Tyler MacDonald wrote:
Adam Kennedy <[EMAIL PROTECTED]> wrote:
So while we are on the subject of META.yml, I think the
dynamic_config
approach is horrible, because it defaults to an efficient error
case and
relies on the author to fix the error, rather than de
On Jul 5, 2006, at 7:47 PM, David Golden wrote:
Some potential options:
(a) Add "directory" as a synonym to the spec and add "dir" as
something that CPAN sites recognize.
(b) Change the spec to "directory" -- if CPAN sites are the only
real user of META.yml no_index, then the pain should
On Tuesday, October 15, 2002, at 07:05 AM, Michael G Schwern wrote:
> This came up at YAPC::Europe. Someone [1] wanted to know if 1/0 would
> produce a divide by zero error in Perl 6, or if it would return a value
> representing an indeterminate result (undef?) It would make more sense
> for
On Wednesday, October 16, 2002, at 04:44 AM, Jonathan Scott Duff wrote:
> People have used the terms "error" and "exception" interchangably in
> this disucssion. To me, an "error" is something that stops program
> execution while an "exception" may or may not stop execution depending
> on what
On Feb 23, 2005, at 6:08 PM, Michael G Schwern wrote:
For any brave Phalanx folks who wish to target MakeMaker I can point
you at
some critically deficient areas of its testing.
1) XS. There is absolutely no testing of XS code. The primary
problem is
determining if the user has a working buil
On Mar 4, 2005, at 4:07 PM, Michael G Schwern wrote:
On Thu, Feb 24, 2005 at 11:47:31AM -0600, Ken Williams wrote:
Better would be to snark it from ExtUtils::CBuilder, which has a
has_compiler() method.
How portable is this? I see there's some minimal VMS and OS/2 code in
there, will it wor
On Mar 28, 2005, at 6:21 PM, Randy W. Sims wrote:
I think someone had proposed a year or two ago that there should be a
test_requires options and I argued against it. Now, I think maybe it
was a good idea; especially, since the number of extra testing modules
being used have increased a lot over
On Mar 30, 2005, at 6:16 PM, Michael G Schwern wrote:
On Wed, Mar 30, 2005 at 05:53:37PM -0500, Randy W. Sims wrote:
Should we completely open this up so that
requires/recommends/conflicts
can be applied to any action?
install_recommends => ...
testcover_requires => ...
etc.
This sounds useful an
On Mar 29, 2005, at 10:44 PM, Randy W. Sims wrote:
Michael G Schwern wrote:
On Tue, Mar 29, 2005 at 08:33:48PM -0500, Randy W. Sims wrote:
A quickie sample implementation to add more meat. I didn't apply yet
mainly because I'm wondering if we shouldn't bail and do a complete
roll-back (eg. don't
On Apr 1, 2005, at 2:55 PM, Christopher H. Laco wrote:
If build, test, and install are considered the critical path, why was
Build/make never changed to simple run "test" always as part of the
builds success or failure?
Just curious. In a way, I'd be much happier if 'perl Build' or 'make'
outri
On Apr 6, 2005, at 7:13 AM, Robert Rothenberg wrote:
Is there a way tests to determine that a module cannot be installed on
a platform so that CPANPLUS or CPAN::YACSmoke can issue an "NA" (Not
Applicable) report?
CPANPLUS relies on module names (e.g. "Solaris::" or "Win32::") but
that is not al
On Apr 8, 2005, at 12:32 PM, Michael G Schwern wrote:
die "NA: $reason";
Since, at the moment, we're having trouble putting together a system to
cover the possible reasons for an NA report let the module author
figure it
out. Its simple and minimal.
I like it.
-Ken
On Mar 30, 2005, at 4:53 PM, Randy W. Sims wrote:
Should we completely open this up so that
requires/recommends/conflicts can be applied to any action?
install_recommends => ...
testcover_requires => ...
etc.
I like it. But for some reason I find it a little scary.
Doing this would require a lit
Some thoughts:
1) In order to be convenient for the code author, he/she should be able
to poll for available clients before submitting a job. My inclination
would be to make this a simple inetd on the client, rather than any
persistent connection between client & server. I think if there were
14 matches
Mail list logo
