Hi,
Twice recently, I've just been through the task of upgrading
CPAN.pm from 1.59_54 to 1.63 on a solaris system because
something about MD5 was broken enough that no modules could be
installed. It took a long time to do manually, because of the
dependency on Test::More, which depends on Te
On Tuesday, September 3, 2002, at 03:10 PM, Michael G Schwern wrote:
> On Tue, Sep 03, 2002 at 11:26:01AM +1000, Ken Williams wrote:
>>>> Thus is you need to be in t this might suit
>>>>
>>>> cd t; perl -Mblib=lib foo/bar.t
>>
>> I'd be h
On Tuesday, September 3, 2002, at 08:56 AM, Michael G Schwern wrote:
> On Mon, Sep 02, 2002 at 08:13:06AM +0100, Nick Ing-Simmons wrote:
>> I understand all that. My point was that while test itself may care
>> where it is run, blib.pm does not mind as much. Also blib.pm's job
>> is to make runn
On Thursday, August 29, 2002, at 05:53 PM, Nicholas Clark wrote:
> For information, my example was from the top of t/integer.t in Storable
> It looks like the same bit of code was cargo-cult cut & pasted (er, by
> me I think) from the other Storable tests (such as freeze.t) where they
> have to
On Thursday, August 29, 2002, at 06:25 PM, Michael G Schwern wrote:
> On Thu, Aug 29, 2002 at 06:23:26PM +1000, Ken Williams wrote:
>> I admit that I was a little surprised to see 'lib' stuff here
>> and not 'blib' stuff. Don't blibs get crea
On Thursday, August 29, 2002, at 05:29 PM, Michael G Schwern wrote:
> There's already the beginnings of something like this in
> t/TestInit.pm, but
> it wasn't updated for the PERL_CORE trick. Nor do I know if it can be
> entirely trusted.
>
> Also, Nick's example is a little odd. You usually
Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 02, 2001 at 04:21:17PM -0500, Dave Rolsky wrote:
>> On Tue, 2 Oct 2001, Michael G Schwern wrote:
>>
>> > Any particularly good reason we're showing all that "PERL_DL_NONLAZY"
>> > noise as part of "make test"? What about just:
>>
>> I d
Dave Rolsky <[EMAIL PROTECTED]> wrote:
> On Tue, 2 Oct 2001, Michael G Schwern wrote:
>
>> Any particularly good reason we're showing all that "PERL_DL_NONLAZY"
>> noise as part of "make test"? What about just:
>
> I do some weird stuff with that piece to pass data around to my tests.
> Sometim
ownloaded and tested without some additional manual system
configuration, because these may well fail in a rapid-fire smoke test.
This includes modules like GD.pm (requires several external libraries)
or HTML::Mason (has interactive 'make test').
---
