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
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
On Mon, Apr 28, 2008 at 5:03 AM, Johan Vromans [EMAIL PROTECTED] wrote:
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.
Applications
On Fri, Apr 25, 2008 at 07:56:37PM -0500, Jonathan Rockway wrote:
That said, I always do this:
(so apps can find libs w/ install_base set)
package MyApp::Script::Whatever;
use Moose;
with 'MooseX::Getopt';
has ...;
sub run { ... }
Then:
#!/usr/bin/env perl
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
On Mon, Apr 28, 2008 at 09:19:37AM -0500, Ken Williams wrote:
On Mon, Apr 28, 2008 at 5:03 AM, Johan Vromans [EMAIL PROTECTED] wrote:
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
# from Austin Schutz
# on Monday 28 April 2008:
.. but when an app is installed by M::B, it has no idea where it's
been installed or where its components are.
This is sort-of true. You would have to intercept the install_map()
during ACTION_install(). I don't know how compatible/robust or
