Re: [Module::Build] codebase? paths in .tar.gz?

[Dave R. <au...@ur...>]

On Fri, 19 Dec 2003, Glenn Linderman wrote:

> "perl build dist" produces errors, and "perl build ppd" produces errors:

You probably don't want to build a PPD unless you understand what the
various things that go in a PPD are.  I'm not an expert on it, but I did
write the PPD-related code for Module::Build, and from what I can gather
you need to actually understand how it will be used, where it will be
installed from, etc., to make it work.

> Unable to add file: 'GFfP-0.1/blib' at
> C:\Perl\site\lib/Module/Build/Base.pm line 1706

This I'll let Ken answer.

> D:\GFfP>perl build ppd
> Cannot create a PPD file unless codebase argument is given
>
>
> Here's my build.pl
>
> use Module::Build;
> my $build = Module::Build->new
>    (
>     module_name => 'GFfP',
>     license => 'restrictive',
>     dist_author => 'Glenn Linderman <pe...@ne...>',
>     requires => { 'perl' => '5.8.0', },
>     codebase => '.',
>    );
> $build->create_build_script;

For some reason I can't recall, I coded it so that codebase can only be
given from the command line via:

 ./Build ppd codebase=.

However, I'm pretty sure a codebase on "." will not work, but I won't
swear to it.

A patch to make codebase settable via the new() method is probably good
thing, right Ken?

> The documentation Module::Build supplies for "codebase" is pretty terse,
> and there are no examples of it in the sample Build.pl file.

That's cause I don't really understand the PPD stuff too well.  I was kind
of hoping some Win32 expert would fill in the the rest.

> And all those warnings from perl build dist are for directories... and
> indeed, the resulting .tar.gz file has a flat structure... the files are
> all there, but their directory structure is not preserved.  As a result,
> I can't distribute the package.

I wonder if it's a permissions problem.

> It'd be nice to have a sample MANIFEST file too, for a sample
> project.

 ./Build manifest

> Seems to me like the Cookbook should have a trivial, but complete,
> example of all the stuff you need to make your own pure perl module, and
> another example with all the stuff you need to make your own XS module.

A module with (simple) XS is handled identically to a pure Perl module.
If you need to specify linker/compiler flags then it's a little different.

>   I know that those sorts of examples would have saved me a lot of time
> today.

Now that you know what they should be, why not submit a patch? ;)


-ave

/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/