Re: Module requirements (was: Module::Build and installing in non-standard locations)

2006-04-05 Thread demerphq
On 4/4/06, A. Pagaltzis [EMAIL PROTECTED] wrote: * demerphq [EMAIL PROTECTED] [2006-04-04 08:05]: Personally i think the core is too big argument is a red-herring given that bandwidth is as cheap as it is these days. Adding a couple of modules to core would increase the rsynch time by

Re: Module requirements (was: Module::Build and installing in non-standard locations)

2006-04-04 Thread A. Pagaltzis
* demerphq [EMAIL PROTECTED] [2006-04-04 08:05]: Personally i think the core is too big argument is a red-herring given that bandwidth is as cheap as it is these days. Adding a couple of modules to core would increase the rsynch time by what a second or two? It would suck up a couple of extra

Re: Module requirements (was: Module::Build and installing in non-standard locations)

2006-04-04 Thread chromatic
On Tuesday 04 April 2006 12:16, A. Pagaltzis wrote: Is it any wonder that people say core is too big? Want more heresy? If the core contained more modules, there'd be even less possibility of getting managed hosts or hostile system administrators in really picky environments to install or

Re: Module requirements (was: Module::Build and installing in non-standard locations)

2006-04-01 Thread Adam Kennedy
A. Pagaltzis wrote: * Adam Kennedy [EMAIL PROTECTED] [2006-04-01 04:10]: I guess the problem is that in Makefile.PL strictly speaking you're not _really_ meant to be doing any building of stuff. That's supposed to be what you do in make. So one solution to your problem might be to add

Re: Module requirements (was: Module::Build and installing in non-standard locations)

2006-03-31 Thread A. Pagaltzis
* demerphq [EMAIL PROTECTED] [2006-03-31 10:10]: Something like dieing on a use warnings statement in the makefile or whatever to me constitutes a pre-build failure, not an install failure. `s/installer/build script/gi` on Adam’s post and his points still stand. The whatever-it’s-called whose

Re: Module requirements (was: Module::Build and installing in non-standard locations)

2006-03-31 Thread Adam Kennedy
A. Pagaltzis wrote: * demerphq [EMAIL PROTECTED] [2006-03-31 10:10]: Something like dieing on a use warnings statement in the makefile or whatever to me constitutes a pre-build failure, not an install failure. `s/installer/build script/gi` on Adam’s post and his points still stand. The

Re: Module requirements (was: Module::Build and installing in non-standard locations)

2006-03-31 Thread A. Pagaltzis
* Adam Kennedy [EMAIL PROTECTED] [2006-04-01 04:10]: I guess the problem is that in Makefile.PL strictly speaking you're not _really_ meant to be doing any building of stuff. That's supposed to be what you do in make. So one solution to your problem might be to add something that defers

Module requirements (was: Module::Build and installing in non-standard locations)

2006-03-30 Thread Randy W. Sims
Adam Kennedy wrote: There are a number of ways to do this. The most simple is: use strict; use warnings; use File::HomeDir; my $conf_dir = File::Spec-catdir( File::HomeDir-my_home, '.Foo' ); Not that I wish to be a pedant about this, but only so people keep it in mind... This