+6.10_06 Sat Jun 7 00:55:29 PDT 2003
+ - Whoops, Liblist.t busted on VMS after I turned strict on in
+ ExtUtils::Liblist::Kid. Merely a test bug, not a real bug.
+ - Fixed metafile_addtomanifest failure so the proper error shows.
+ - Fixed metafile_addtomanifest failure diagnostic leaking out during
+ the basic.t test on Windows.
+
6.10_05 Fri Jun 6 18:15:30 PDT 2003
* Documenting META.yml, NO_META
* Documenting the fact that distdir will auto generate META.yml and
use strict;
use vars qw($VERSION @ISA);
-$VERSION = 0.05;
+$VERSION = 0.06;
@ISA = qw(File::Spec);
use Config;
my $add_meta = $self->oneliner(<<'CODE', ['-MExtUtils::Manifest=maniadd']);
eval { maniadd({q{META.yml} => q{Module meta-data (added by MakeMaker)}}) }
- or warn "Could not add META.yml to MANIFEST: $@\n"
+ or print "Could not add META.yml to MANIFEST: $${'@'}\n"
CODE
return sprintf <<'MAKE_FRAG', $add_meta;
package ExtUtils::MakeMaker::FAQ;
-(our $VERSION) = sprintf "%03d", q$Revision: 1.6 $ =~ /Revision:\s+(\S+)/;
+(our $VERSION) = sprintf "%03d", q$Revision: 1.7 $ =~ /Revision:\s+(\S+)/;
1;
__END__
Simplest way to do it automatically is to use your version control
system's revision number (you are using version control, right?).
-In CVS and RCS you use $Revision: 1.6 $ writing it like so:
+In CVS and RCS you use $Z<>Revision$ writing it like so:
- $VERSION = sprintf "%d.%03d", q$Revision: 1.6 $ =~ /(\d+)/g;
+ $VERSION = sprintf "%d.%03d", q$Revision$ =~ /(\d+)/g;
-On your next check in, $Revision: 1.6 $ will magically be expanded to contain
+On your next check in, $Z<>Revision$ will magically be expanded to contain
the current revision #.
- $VERSION = sprintf "%d.%03d", q$Revision: 1.6 $ =~ /(\d+)/g;
+ $VERSION = sprintf "%d.%03d", q$Revision: 1.7 $ =~ /(\d+)/g;
-Every time the file is checked in the $Revision: 1.6 $ will be updated,
+Every time the file is checked in the $Z<>Revision$ will be updated,
updating your $VERSION.
In CVS version 1.9 is followed by 1.10. Since CPAN compares version
numbers numerically we use a sprintf() to convert 1.9 to 1.009 and
1.10 to 1.010 which compare properly.
-If branches are involved (ie. $Revision: 1.5.3.4) its a little more
+If branches are involved (ie. $Z<>Revision: 1.5.3.4) its a little more
complicated.
# must be all on one line or MakeMaker will get confused.
- $VERSION = do { my @r = (q$Revision: 1.6 $ =~ /\d+/g); sprintf "%d."."%03d" x $#r, @r };
+ $VERSION = do { my @r = (q$Revision$ =~ /\d+/g); sprintf "%d."."%03d" x $#r, @r };
+=item What's this F<META.yml> thing and how did it get in my F<MANIFEST>?!
+
+F<META.yml> is a module meta-data file pioneered by Module::Build and
+automatically generated as part of the 'distdir' target (and thus
+'dist'). See L<ExtUtils::MakeMaker/"Module Meta-Data">.
+
+To shut off its generation, pass the C<NO_META> flag to C<WriteMakefile()>.
=back
my @warn;
local $SIG{__WARN__} = sub {push @warn, [@_]};
- my @out = ExtUtils::Liblist->ext('-ln0tt43r3_perl');
+ my $ll = bless {}, 'ExtUtils::Liblist';
+ my @out = $ll->ext('-ln0tt43r3_perl');
is( @out, 4, 'enough output' );
unlike( $out[2], qr/-ln0tt43r3_perl/, 'bogus library not added' );
ok( @warn, 'had warning');