Ok, so here's what must be a question with a really simple answer:
how do I write a perl app?
For example: I want to display a jpeg.
MyApp/script/display.pl:
#!/path/to/perl
use Myapp::Display;
Myapp::Diplay->new()->display('example.jpg');
__END__
MyApp/lib/Myapp/Display.pm
.
I think you need PAR
-Original Message-
From: Austin Schutz [mailto:[EMAIL PROTECTED]
Sent: Friday, April 25, 2008 10:43 PM
To: module-authors@perl.org
Subject: Application Building
Ok, so here's what must be a question with a really simple answer:
how do I write a per
TED]
> Sent: Friday, April 25, 2008 10:43 PM
> To: module-authors@perl.org
> Subject: Application Building
>
> Ok, so here's what must be a question with a really simple answer:
> how do I write a perl app?
>
> For example: I want to display a jpeg.
>
You really didn't say much about what you're trying to do. You said you
did some stuff and some other stuff didn't happen. It's hard to help
you -- what *exactly* is the problem? (There are plenty of things that
install and run apps on the CPAN. App::Ack comes to mind. It Just
Works, there is
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 stan
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 sc
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.
>
> Appli
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
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 o
On Mon, 2008-28-04 at 18:46 +0200, Johan Vromans wrote:
> 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
Thanks. I missed
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.
# 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
d
12 matches
Mail list logo
