On Mon, 2008-28-04 at 12:03 +0200, Johan Vromans wrote:
> Jonathan Rockway <[EMAIL PROTECTED]> writes:
>
> > There are plenty of things that install and run apps on the CPAN.
> > App::Ack comes to mind. It Just Works, there is nothing special you
> > need to do.
>
> App::Ack (and all the other scripts that 'just work') require
> everything to be installed in the standard Perl location. If your
> modules are in @INC, everything just works.
>
> What Austin tries to do it to build an app that can be installed as an
> app, not as a Perl module. And then it is suddenly not as easy
> anymore. There's no support from EU::MM and M::B for installing apps.
What about Module::Install ?
[snip]
> First is, how can the app script find its modules. For the most
our $lib;
BEGIN { $lib = 'path/to/lib' }
use lib $lib;
Edit 'path/to/lib' on install. EU::MM has support for editing modules
on install 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.
--gh
