Re: Adding additional targets to Module::Install

You can use postamble to add things to the end of the generated Makefile

postamble <<END_OF_MAKEFILE;
pod:
\t\$(PERL) etc/build_pod.pl
END_OF_MAKEFILE
[download]

So your Makefile.PL will look like:

use inc::Module::Install;

name     'DBIx-Cookbook';
all_from 'lib/DBIx/Cookbook.pm';
author   q{Terrence Brannon <metaperl@gmail.com>};
license  'perl';

author_tests('xt');

build_requires 'Test::More';

requires 'DBI';
requires 'MooseX::App::Cmd';

auto_install;

postamble <<END_OF_MAKEFILE;
pod:
\t\$(PERL) etc/build_pod.pl
END_OF_MAKEFILE

WriteAll;
[download]

Comment on Re: Adding additional targets to Module::Install Select or Download Code

Replies are listed 'Best First'.
Re^2: Adding additional targets to Module::Install by metaperl (Curate) on Apr 14, 2010 at 17:45 UTC
Many thanks! I looked through the Module::Install docs after reading your post, but saw no mention of postamble. Should I have been able to figure out the `postamble` part myself from some docs somewhere? Here is what I ended up adding... it works `postamble <<EOPOST; pod: perl etc/build_pod.pl release: pod tardist echo "ready for release" EOPOST` [download] The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development. -- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Adding additional targets to Module::Install
by metaperl (Curate) on Apr 14, 2010 at 17:45 UTC

Module::Install

postamble

Here is what I ended up adding... it works

postamble <<EOPOST;
pod:
    perl etc/build_pod.pl

release: pod tardist
    echo "ready for release"
EOPOST
[download]

The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development.

-- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"

[reply]
[d/l]
[select]