use Module::Build;
my $class = Module::Build->subclass (
code => q|
use Module::Build::ModuleInfo;
use Pod::Text;
sub create_readme {
my ($self) = @_;
# Say what we are doing.
print "Deleting ChangeLog\n";
unlink 'ChangeLog';
print "Creating ChangeLog\n";
# Get the POD-formatted text.
open my $outfile, '>', 'ChangeLog.pod';
# I'm a bit worried about the 'inc' here: it looks UNIX-only.
# However, M::B won't give my the path directly, and I don't feel like
+ going through contortions.
# (Besides, no one but me should ever run this.)
push my @modules, Module::Build::ModuleInfo->new_from_module(
'Acme::Module', collect_pod =>1
, inc => [$self->base_dir()."/lib"]);
push @modules, Module::Build::ModuleInfo->new_from_module(
'Acme::Module::2', collect_pod =>1
, inc => [$self->base_dir()."/lib"]);
foreach my $pm_file ( @modules ) {
print $outfile "=head1 Changes in: ". $pm_file->name() ."\
+n\n";
print $outfile $pm_file->pod('HISTORY');
}
close $outfile;
# Reformat to standard text, and remove temp file.
my $text = Pod::Text->new();
$text->parse_from_file('ChangeLog.pod', 'ChangeLog');
unlink 'ChangeLog.pod';
}
|
);
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|