demerphq wrote:
On 3/31/06, Adam Kennedy <[EMAIL PROTECTED]> wrote:
If an installer can't INSTALL under battle conditions, it is failing
it's primary missing.
Personally I think its worth being a touch more specific with your language.
I dont see Module::Build's job to be to "install". I see its job as
being to "build". It should, and does leave the job of "installing" to
ExtUtils::Install. And that makes sense to me.
So it seems to be that you have four (five?) phases:
Pre-Build
Build
Test
Install
(Post Install Test?)
Something like dieing on a use warnings statement in the makefile or
whatever to me constitutes a pre-build failure, not an install
failure.
I'd consider that to be just a case of semantics.
I could well argue it doesn't "build" either, it $smaller_divisions_again.
From a top level tasks perspective, Module::Build has two primary roles.
1. Package the module into a distribution.
2. Install the distribution onto a system
Those 4(5) steps are all part of the "install" task.
Most end users don't see the "build" stage as being somehow distinct,
all they want to do is "install a module".
Adam K
