Re: Module::Build 0.30 is released - ppm.t on VMS depends on Archive::Tar patch.

Jos I. Boumans wrote: Hi John, On Oct 1, 2008, at 2:51 AM, John E. Malmberg wrote: http://www.nntp.perl.org/group/perl.vmsperl/2008/06/msg14821.html The main problem is that Archive::Tar needs a patch to properly be able to pack a VMS binary into a tarball. We were waiting for word from

Re: Module::Build 0.30 is released - ppm.t on VMS depends on Archive::Tar patch.

On Wed, Oct 1, 2008 at 12:00 PM, Steve Hay [EMAIL PROTECTED] wrote: Blead is now updated to Archive-Tar-1.39_04 in #34452. One local change remains in blead: Change 32352 by [EMAIL PROTECTED] on 2007/11/16 23:46:13 The new Archive::Tar tests are TODO on VMS for reasons unrelated

RE: Module::Build 0.30 is released - ppm.t on VMS depends on Archive::Tar patch.

John E. Malmberg wrote: Jos I. Boumans wrote: Hi John, On Oct 1, 2008, at 2:51 AM, John E. Malmberg wrote: http://www.nntp.perl.org/group/perl.vmsperl/2008/06/msg14821.html The main problem is that Archive::Tar needs a patch to properly be able to pack a VMS binary into a tarball.

Re: Module::Build 0.30 is released

On Tue, Sep 30, 2008 at 6:33 AM, Steve Hay [EMAIL PROTECTED] wrote: Thanks, applied to bleadperl as 34446. Two local changes remain: Change 32357 by [EMAIL PROTECTED] on 2007/11/17 04:19:47 Skip Module::Build ppm test -- not ready for prime time on VMS. (ppm.t) Change 32351 by

Re: How To Bundle Module::Build (was Re: Module::Build 0.30 is released)

True, but it's FAR more palatable to say Just upgrade ONCE, and you'll never have to think about it again compared to upgrading continuously. Adam K 2008/9/30 Matt S Trout [EMAIL PROTECTED]: If the world upgraded regularly, Module::Build wouldn't be such a disaster anyway :)

Other suggestions for modules that need an updated toolchain? (was latest.pm, Module::Build, etc.)

I've been following the threads here and on p5p about autobundling for Module::Build, using latest.pm etc., and I have to say that the I find the growing complexity required to be backward compatible a bit disturbing. As some have noted, CPAN.pm supports configure_requires and CPANPLUS will soon,

how can I building my own cpan server with old modules?

I don't want the latest and breakest of CPAN. Assuming I have a list of modules with the appropriate *old* version numbers that I know my application is working with. I would like to be able to point my *old* CPAN.pm to a CPAN mirror that carries exactly those modules with exactly those versions.

Re: Other suggestions for modules that need an updated toolchain? (was latest.pm, Module::Build, etc.)

On Thu, Oct 2, 2008 at 8:01 AM, David Golden [EMAIL PROTECTED] wrote: As some have noted, CPAN.pm supports configure_requires and CPANPLUS will soon, so to me it seems like the a better problem to address is how to get an end-user to upgrade those. Not everyone likes to use CPAN{PLUS} to

Re: How To Bundle Module::Build (was Re: Module::Build 0.30 is released)

2008/9/30 Matt S Trout [EMAIL PROTECTED]: If the world upgraded regularly, Module::Build wouldn't be such a disaster anyway :) Adam Kennedy wrote: True, but it's FAR more palatable to say Just upgrade ONCE, and you'll never have to think about it again compared to upgrading continuously.

Re: Other suggestions for modules that need an updated toolchain? (was latest.pm, Module::Build, etc.)

On Thu, Oct 2, 2008 at 9:49 AM, Ken Williams [EMAIL PROTECTED] wrote: That's not necessary when using latest.pm either. Unless latest.pm is buggy. Or unless a new Module::Build fixes some bug or changes some internal function that some distribution happened to depend upon. (Leaving aside the

Re: Other suggestions for modules that need an updated toolchain? (was latest.pm, Module::Build, etc.)

On Thu, Oct 2, 2008 at 11:23 AM, David Golden [EMAIL PROTECTED] wrote: Note -- I'm not saying *don't* do latest.pm and M::B bundling, as some authors may prefer that -- I'm all in favor of M::B being everything that people want and moving away from make as a Perl build tool. Absolutely - this

Re: How To Bundle Module::Build (was Re: Module::Build 0.30 is released)

Michael G Schwern wrote: 2008/9/30 Matt S Trout [EMAIL PROTECTED]: If the world upgraded regularly, Module::Build wouldn't be such a disaster anyway :) Adam Kennedy wrote: True, but it's FAR more palatable to say Just upgrade ONCE, and you'll never have to think about it again compared to

Re: how can I building my own cpan server with old modules?

In article [EMAIL PROTECTED], Gabor Szabo [EMAIL PROTECTED] wrote: So how can I build such a CPAN mirror along with its index files? Which part of the process are you hung up on? The only part that's a pain is getting the list of modules from a distribution so you can feed it to

Re: overriding ~mumble~latest.pm

Quoth [EMAIL PROTECTED] (Eric Wilhelm): # from Ben Morrow # on Thursday 02 October 2008: Being able to install latest.pm[1] and use an installed version doesn't help, though. If there's a bug in the section of latest.pm that tries to locate the installed copy of itself and use it

Re: overriding ~mumble~latest.pm

# from Ricardo SIGNES # on Thursday 02 October 2008: That's not what latest.pm does.  The caller is expected to setup the @INC correctly for use latest -- *then* latest::import() figures out where the __THING YOU ACTUALLY WANT TO LOAD__ is. Is that clear?  Or, you could just read the code: