Re: Best practices for dual-lifing a core module?

[Ken Williams]

On Mar 22, 2007, at 4:39 PM, David Landgren wrote:
Do I just make sure that I can pull the .t file and the .pm file,  
wherever they may wind up in the distribution layout, and diff them  
against those two files in blead? I can't see the point of stuffing  
all the ancillary distribution files into the blead tarball when  
the .pm and .t will be enough. What do other people do/have other  
people done?

For Module::Build and PathTools, I use little scriptoids to create  
patch output for me.  The script for Module::Build is below.

 -Ken

===========================
#!/usr/bin/perl

# A script to check a local copy of M::B against bleadperl, generating
# a blead patch if they're out of sync.  An optional directory
# argument will be chdir()-ed into before comparing.

# There are still a couple of holes here that need plugging, though.

use strict;
chdir shift() if @ARGV;

my $bleadstart = "~/Downloads/perl/bleadperl/lib/Module/Build";

diff("$bleadstart.pm", "lib/Module/Build.pm" );

diff($bleadstart, "lib/Module/Build",
     qw(t Changes));

diff("$bleadstart/Changes", "Changes" );

diff("$bleadstart/t", "t" );

######################
sub diff {
  my ($first, $second, @skip) = @_;
  local $_ = `diff -ur $first $second`;

  s/^Only in .*~\n//mg;

  for my $x (@skip) {
    s/^Only in .* $x\n//m;
  }
  print unless defined wantarray;
  return $_;
}
===========================