package ExtUtils::MakeMaker::Tutorial;
-use vars qw($VERSION);
-$VERSION = 0.01;
+our $VERSION = 0.02;
=head1 NAME
=item Makefile.PL
When you run Makefile.PL, it makes a Makefile. That's the whole point of
-MakeMaker. The Makefile.PL is a simple module which loads
-ExtUtils::MakeMaker and runs the WriteMakefile() function with a few
-simple arguments.
+MakeMaker. The Makefile.PL is a simple program which loads
+ExtUtils::MakeMaker and runs the WriteMakefile() function to generate a
+Makefile.
Here's an example of what you need for a simple module:
MANIFEST
lib/Your/Module.pm
-Filepaths in a MANIFEST always use Unix conventions (ie. /) even if you're
+File paths in a MANIFEST always use Unix conventions (ie. /) even if you're
not on Unix.
You can write this by hand or generate it with 'make manifest'.
+See L<ExtUtils::Manifest> for more details.
+
=item lib/
This is the directory where your .pm and .pod files you wish to have
installed go. They are layed out according to namespace. So Foo::Bar
-is lib/Foo/Bar.pm.
+is F<lib/Foo/Bar.pm>.
=item t/
Tests for your modules go here. Each test filename ends with a .t.
-So t/foo.t. 'make test' will run these tests. The directory is flat,
+So F<t/foo.t>/ 'make test' will run these tests. The directory is flat,
you cannot, for example, have t/foo/bar.t run by 'make test'.
Tests are run from the top level of your distribution. So inside a test
A file full of regular expressions to exclude when using 'make
manifest' to generate the MANIFEST. These regular expressions
-are checked against each filepath found in the distrubtion (so
+are checked against each file path found in the distribution (so
you're matching against "t/foo.t" not "foo.t").
Here's a sample:
L<perlnewmod> gives more information about how to write a module.
There are modules to help you through the process of writing a module:
-L<ExtUtils::ModuleMaker>, L<Module::Setup>, L<CPAN::MakeMaker>
+L<ExtUtils::ModuleMaker>, L<Module::Install>, L<PAR>
=cut