BEGIN {require 5.005_03;}
-$VERSION = '6.10_04';
-($Revision) = q$Revision: 1.111 $ =~ /Revision:\s+(\S+)/;
+$VERSION = '6.15';
+($Revision) = q$Revision: 1.130 $ =~ /Revision:\s+(\S+)/;
require Exporter;
use Config;
dynamic_lib=> 'hash',
linkext => 'hash',
macro => 'hash',
+ postamble => 'hash',
realclean => 'hash',
test => 'hash',
tool_autosplit => 'hash',
my $key;
for $key (@Prepend_parent) {
next unless defined $self->{PARENT}{$key};
+
+ # Don't stomp on WriteMakefile() args.
+ next if defined $self->{ARGS}{$key} and
+ $self->{ARGS}{$key} eq $self->{$key};
+
$self->{$key} = $self->{PARENT}{$key};
+
unless ($Is_VMS && $key =~ /PERL$/) {
$self->{$key} = $self->catdir("..",$self->{$key})
unless $self->file_name_is_absolute($self->{$key});
$self->init_dist;
$self->init_INST;
$self->init_INSTALL;
+ $self->init_DEST;
$self->init_dirscan;
$self->init_xs;
$self->init_PERL;
This is the root directory into which the code will be installed. It
I<prepends itself to the normal prefix>. For example, if your code
-would normally go into /usr/local/lib/perl you could set DESTDIR=/tmp
+would normally go into /usr/local/lib/perl you could set DESTDIR=/tmp/
and installation would go into /tmp/usr/local/lib/perl.
This is primarily of use for people who repackage Perl modules.
-From the GNU Makefile conventions.
+NOTE: Due to the nature of make, it is important that you put the trailing
+slash on your DESTDIR. "/tmp/" not "/tmp".
=item DIR
Boolean. Attribute to inhibit descending into subdirectories.
+=item NO_META
+
+When true, suppresses the generation and addition to the MANIFEST of
+the META.yml module meta-data file during 'make distdir'.
+
+Defaults to false.
+
=item NO_VC
In general, any generated Makefile checks for the current version of
$VERSION = '1.00';
*VERSION = \'1.01';
- $VERSION = sprintf "%d.%03d", q$Revision: 1.111 $ =~ /(\d+)/g;
+ $VERSION = sprintf "%d.%03d", q$Revision: 1.130 $ =~ /(\d+)/g;
$FOO::VERSION = '1.10';
*FOO::VERSION = \'1.11';
our $VERSION = 1.2.3; # new for perl5.6.0
=head2 Additional lowercase attributes
can be used to pass parameters to the methods which implement that
-part of the Makefile.
+part of the Makefile. Parameters are specified as a hash ref but are
+passed to the method as a hash.
=over 2
{ANY_MACRO => ANY_VALUE, ...}
+=item postamble
+
+Anything put here will be passed to MY::postamble() if you have one.
+
=item realclean
{FILES => '$(INST_ARCHAUTODIR)/*.xyz'}
directory with the name C<$(DISTNAME)-$(VERSION)>. If that directory
exists, it will be removed first.
+Additionally, it will create a META.yml module meta-data file and add
+this to your MANFIEST. You can shut this behavior off with the NO_META
+flag.
+
=item make disttest
Makes a distdir first, and runs a C<perl Makefile.PL>, a make, and
WriteMakefile( 'dist' => { COMPRESS=>"bzip2", SUFFIX=>".bz2" })
+
+=head2 Module Meta-Data
+
+Long plaguing users of MakeMaker based modules has been the problem of
+getting basic information about the module out of the sources
+I<without> running the F<Makefile.PL> and doing a bunch of messy
+heuristics on the resulting F<Makefile>. To this end a simple module
+meta-data file has been introduced, F<META.yml>.
+
+F<META.yml> is a YAML document (see http://www.yaml.org) containing
+basic information about the module (name, version, prerequisites...)
+in an easy to read format. The format is developed and defined by the
+Module::Build developers (see
+http://module-build.sourceforge.net/META-spec.html)
+
+MakeMaker will automatically generate a F<META.yml> file for you and
+add it to your F<MANIFEST> as part of the 'distdir' target (and thus
+the 'dist' target). This is intended to seamlessly and rapidly
+populate CPAN with module meta-data. If you wish to shut this feature
+off, set the C<NO_META> C<WriteMakefile()> flag to true.
+
+
=head2 Disabling an extension
If some events detected in F<Makefile.PL> imply that there is no way