Re: [Module-build-general] Re: META.yaml in Module-Build dist

[Ken W. <ke...@ma...>]

On Wednesday, August 14, 2002, at 08:43 PM, Graham Barr wrote:
> After sending this I started to compare with what MM does.
>
> With MM you pass NAME and VERSION or VERSION_FROM. Where NAME
> is a module name. You can optionally pass DISTNAME
>
> and DISTNAME defaults to NAME =~ s/::/-/g
>
> So maybe all that sneeded is for another method + yaml entry
> for distname.

Yeah, that's close to what I'm thinking.  Here's my current proposal:

  1) Replace module_version and module_version_from parameters 
with dist_version and dist_version_from.  They really were facts 
about the distribution anyway, but I didn't realize it.

  2) Create a dist_name parameter which is essentially the same 
as MakeMaker's NAME parameter.

  3) Make module_name into a shortcut for setting dist_name and 
dist_version_from in one go.  This handles the most common case 
nicely, in which a distribution houses a single "chief" module.

I don't think I have a problem with the backward-compatibility 
breakage of 1).  2) and 3) don't have any such problems.


> Also read your docs. The autosplit call. Why do you need it ?
> MM does a scan of each .pm for /^use AutoSplit/ to determine
> which need splitting.

I can't actually find that in the MM source, can you point me to it?

I know it was happening *somehow* automatically, though.  Part 
of the reason I changed it was that I didn't like the magical 
scanning of code in MM.  I think the scanning for $VERSION is 
unfortunately quite necessary, but I'd like for that to be the 
only code scanning if possible.

  -Ken