Re: [Module::Build] [PATCH] ppm_dist action

[Randy K. <ra...@th...>]

On Wed, 14 Jan 2004, Ken Williams wrote:

> On Tuesday, January 13, 2004, at 08:46  PM, Randy W. Sims wrote:
>
> >> * For backwards compatibility (not really sure it's
> >> neccessary at this point, but...) I'd suggest leaving
> >> the 'ppd' action as is, and create a new 'ppm_dist'
> >> action that runs the 'ppd' action and creates an
> >> archive of the blib directory, running the 'build'
> >> action if neccessary. Ken?
> >
> > Attached is a patch that adds a new 'ppm_dist' action.
> > It accepts a 'codebase' argument just like the 'ppd'
> > action. This action runs the 'ppd' action and then
> > builds an archive of the blib directory. Glenn, this
> > should allow you to "install on the same machine it is
> > built on".  The 'ppd' action remains unchanged. Please
> > let me know if this patch is correct.
>
> It changes the semantics of the make_tarball() method a
> bit - I think we probably also want to make the tarball
> unpack to a name matching the filename people download.
> So I think maybe we should copy blib/ to a new directory
> (once the naming issue is solved) and then tarball it up,
> using the same old make_tarball() method.

Unfortunately, the ppm utility is pretty picky about
about the structure of the associated codebase archive -
it can have any name one wants (as long as it's specified
as such in the ppd file), but it should unpack into a
top-level blib/ directory, so as to have the structure
   blib/arch/
   blib/bin/
   blib/lib/
etc. As well, if one wanted to include html documentation,
it should go under
  blib/html/site/lib/
If ppm finds such html docs, it will install them in the
user's Perl/html/ tree, and update the main index.html
accordingly. If there's interest, I have some code around
that could generate such docs from the pod/pm files in the
distribution - it wouldn't be too hard to supply a M::B
patch to do so.

-- 
best regards,
randy