On Thu, Jan 21, 2010 at 8:12 AM, Johan Vromans <[email protected]> wrote: > [Quoting David Golden, on January 21 2010, 06:30, in "Re: CPAN Testers Dai"] >> It's just the packlist that gets installed with Module::Build. I.e. >> by ExtUtils::Packlist. All this means is that you can't bundle on a >> Perl that came with M::B 0.36+ because there are no packlists for >> modules distributed with the Perl core. (That is an issue I haven't >> had a chance to pursue with p5p.) > > Again, does that mean I have to include a packlist with absolute file > names derived from the build system that may (will) not correspond to > the file names used on the target system?
No -- the packlist is used to determine which files to bundle. It's actually remarkably hard to know what files belong to a given module once they've been installed. Packlists sort of work, but aren't ideal. I suspect the ultimate answer is to treat inc/ like a local::lib directory and install things from original CPAN distributions (with dependencies). It reminds me of that line in Aliens: "I say we take off and nuke the site from orbit -- it's the only way to be sure" > Thanks for the answers, pointers, patience, and the nice tools. You're welcome. Thanks for being patient with the evolving state of tools and offering constructive complaints instead of just saying "you suck!" :-) David
