Guy Hulbert <[EMAIL PROTECTED]> writes:
> What about Module::Install ?
I've had several discussions on whether to use EU::MM, M::B or M::I.
It was made very clear to me that M::I is too limited and crippled to
be useful for anything but trivial installs (that are more robustly
dealt with by the other two anyway).
> > First is, how can the app script find its modules. For the most
>
> our $lib;
> BEGIN { $lib = 'path/to/lib' }
> use lib $lib;
How would that be different from
use lib 'path/to/lib';
> Edit 'path/to/lib' on install.
Sure.
> EU::MM has support for editing modules on install
Sure. But not trivially.
> ... but since I am building a fairly large app, I've made it self
> installing. I also want to make sure that no-one can break it by
> polluting its name space and 'use lib' ensures that its own modules
> are found first.
This is exactly the point I'm trying to make. Apparently the current
mechanisms are not sufficient to install non-trivial apps. This forces
you to write your own.
-- Johan
