New assertions in Ruby

2008-02-11 Thread Andy Lester
Some interesting ideas for how the Ruby folks are now doing their unit testing. http://www.oreillynet.com/ruby/blog/2008/02/assert2.html xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: expanding the cpan script, and Module

2008-02-11 Thread David Golden
On Feb 11, 2008 9:05 PM, Matisse Enzer <[EMAIL PROTECTED]> wrote: > > Right -- you're not handing off all arguments to CPAN::Shell at once. > > However, I think he wanted CPAN.pm to halt if any *dependencies* > > failed as well as anything specified to the "cpan" script -- that > > requires a chang

Re: expanding the cpan script, and Module

2008-02-11 Thread Andrew Hampe
On Feb 11, 2008, at 1:20 PM, Michael G Schwern wrote: I believe you want to send this along to the CPAN bug tracker. perl- qa is for quality assurance (testing) issues. http://rt.cpan.org/NoAuth/Bugs.html?Dist=CPAN But it's trivial to do yourself. use CPAN; for my $name (@A

Re: expanding the cpan script, and Module

2008-02-11 Thread Matisse Enzer
On Feb 11, 2008, at 5:01 PM, David Golden wrote: On Feb 11, 2008 6:52 PM, brian d foy <[EMAIL PROTECTED]> wrote: That's not really true. Although I use CPAN::Shell for some things, cpan isn't just passing things along. My program is a different interface using the same backend. Right -- you'

Re: expanding the cpan script, and Module

2008-02-11 Thread David Golden
On Feb 11, 2008 6:52 PM, brian d foy <[EMAIL PROTECTED]> wrote: > That's not really true. Although I use CPAN::Shell for some things, > cpan isn't just passing things along. My program is a different > interface using the same backend. Right -- you're not handing off all arguments to CPAN::Shell a

Re: ignoring already installed modules during a cpan install

2008-02-11 Thread brian d foy
[[ This message was both posted and mailed: see the "To," "Cc," and "Newsgroups" headers for details. ]] In article <[EMAIL PROTECTED]>, Andrew Hampe <[EMAIL PROTECTED]> wrote: > is there an existing, or planned setting, for the CPAN utilities, that > will cause it to ignore any already inst

Re: expanding the cpan script, and Module

2008-02-11 Thread brian d foy
In article <[EMAIL PROTECTED]>, David Golden <[EMAIL PROTECTED]> wrote: > It sounds like what you really want is a new config option. The > "cpan" script is just a pass-through to CPAN::Shell. That's not really true. Although I use CPAN::Shell for some things, cpan isn't just passing things alon

Re: expanding the cpan script, and Module

2008-02-11 Thread brian d foy
[[ This message was both posted and mailed: see the "To," "Cc," and "Newsgroups" headers for details. ]] In article <[EMAIL PROTECTED]>, Andrew Hampe <[EMAIL PROTECTED]> wrote: > Desrired Behavior: > running a cpan session, with the flag set, will cause the session to > note the error and >

Re: expanding the cpan script, and Module

2008-02-11 Thread Michael G Schwern
Andrew Hampe wrote: The Basic CPAN concern: --bail_on_fail flag (2008.02.10 ) Problem description: when a cpan session is looking for more than one distribution/module there needs to be a way to 'flag' that the session must fail and stop if there is an error loading any distribution,

Re: expanding the cpan script, and Module

2008-02-11 Thread David Cantrell
Andrew Hampe wrote: The Basic CPAN concern: --bail_on_fail flag (2008.02.10 ) Problem description: when a cpan session is looking for more than one distribution/module there needs to be a way to 'flag' that the session must fail and stop if there is an error loading any distribution

Re: ignoring already installed modules during a cpan install

2008-02-11 Thread David Golden
On Feb 11, 2008 4:04 PM, chromatic <[EMAIL PROTECTED]> wrote: > On Monday 11 February 2008 12:53:35 Andrew Hampe wrote: > > > is there an existing, or planned setting, for the CPAN utilities, that > > will cause it to ignore any already installed dependencies, during an > > installation, except for

Re: ignoring already installed modules during a cpan install

2008-02-11 Thread chromatic
On Monday 11 February 2008 12:53:35 Andrew Hampe wrote: > is there an existing, or planned setting, for the CPAN utilities, that   > will cause it to ignore any already installed dependencies, during an   > installation, except for modules installed during the current session.   Is this not the w

Re: expanding the cpan script, and Module

2008-02-11 Thread David Golden
It sounds like what you really want is a new config option. The "cpan" script is just a pass-through to CPAN::Shell. I suggest posting your request to the CPAN.pm RT queue -- Andreas (and others like me) monitor it and it keeps the backlog of bugs and feature requests in one place. I'm a little

ignoring already installed modules during a cpan install

2008-02-11 Thread Andrew Hampe
volks, is there an existing, or planned setting, for the CPAN utilities, that will cause it to ignore any already installed dependencies, during an installation, except for modules installed during the current session. For example: cpan install Foo if Foo depends on Bar, and Bar

expanding the cpan script, and Module

2008-02-11 Thread Andrew Hampe
volks, The Basic CPAN concern: --bail_on_fail flag (2008.02.10 ) Problem description: when a cpan session is looking for more than one distribution/module there needs to be a way to 'flag' that the session must fail and stop if there is an error loading any distribution, or a s

Re: cpan-testers in the inbox

2008-02-11 Thread Jonathan Rockway
* On Mon, Feb 11 2008, Andy Lester wrote: > http://log.perl.org/2008/02/no-more-email-d.html > > Well I guess that settles that. :) This is unrelated to the usual whining about receiving FAIL reports in your inbox. Those are sent directly by the smoker, not via the cpan-testers mailing list. The

cpan-testers in the inbox

2008-02-11 Thread Andy Lester
http://log.perl.org/2008/02/no-more-email-d.html Well I guess that settles that. :) xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Process Boundaries and Aggregated Tests

2008-02-11 Thread Ovid
So far we've been quite happy with Test::Aggregate here at work. It's one of a number of strategies we've used to improve our test suite performance, something we desperately need (7.1 minutes down to 3.6 minutes for aggregated tests). That being said, the process boundary issue that Eric Wilhelm