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
> > rsyn
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 up
* 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
>
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 someth
* 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
>
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 wha
* 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 wh
On Thu, 30 Mar 2006, Randy W. Sims wrote:
> Note that the entries in install_path must have the same name as
> supplied to add_build_element() (not with the '_files' appendage).
OK - thanks again, that is my problem... the naming of the entries...
I was too dense to appreciate your note about th
Matisse Enzer wrote:
On Tue, 28 Mar 2006, Randy W. Sims 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' );
use Module::Build;
my $builder = Module::Build->new(
On Tue, 28 Mar 2006, Randy W. Sims 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' );
>
> use Module::Build;
> my $builder = Module::Build->new(
>
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
> min
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 installer will crash with a non-
On Tue, 28 Mar 2006, Randy W. Sims wrote:
> The add_build_element() method is the key to the process.
Ah-Ha and thank you Very Nice!
I did read the perldoc - but just didn't get that
add_build_element('foo_files')
would make M::B look for a foo_fiels element - and I thought i would have
to
Matisse Enzer wrote:
What's the standard (if any) for how to configure a build script to
install specific files (e.g. httpd.conf) in someplace other than the
standard Perl library/script/man locations?
For example, if my distro contains a bunch of .pm files and .pl files,
which go in the "nor
What's the standard (if any) for how to configure a build script to
install specific files (e.g. httpd.conf) in someplace other than the
standard Perl library/script/man locations?
For example, if my distro contains a bunch of .pm files and .pl files,
which go in the "normal" place, and my dis
15 matches
Mail list logo
