Ken Williams <[EMAIL PROTECTED]> wrote:
> I agree on the personal rights aspect here. =) I'd still recommend
> that people include a Makefile.PL, but we can't force it. That would
> just mean people would have to find creative method to break the
> enforcement if they really know what they're doing.
With that in mind, I decided to see what happens with the most
minimal build.PL possible. It ends up being this:
use Module::Build;
Module::Build->new(
'dist_name','foo',
'dist_version',0.01,
'dist_author','me',
'dist_abstract','you bet'
)->create_build_script;
[EMAIL PROTECTED]:~/dev/foo$ perl Build.PL
Checking prerequisites...
Looks good
Creating new 'Build' script for 'foo' version '0.01'
[EMAIL PROTECTED]:~/dev/foo$ ./Build distdir
No license specified, setting license = 'unknown'
Deleting META.yml
Creating META.yml
WARNING: Possible missing or corrupt 'MANIFEST' file.
Nothing to enter for 'provides' field in META.yml
Can't create distdir without a MANIFEST file - run 'manifest' action first
at /usr/local/share/perl/5.8.7/Module/Build/Base.pm line 2754.
[EMAIL PROTECTED]:~/dev/foo$ ./Build manifest
File 'MANIFEST.SKIP' does not exist: Creating a default 'MANIFEST.SKIP'
Added to MANIFEST: Build.PL
Added to MANIFEST: MANIFEST
Added to MANIFEST: META.yml
[EMAIL PROTECTED]:~/dev/foo$ ./Build distdir
No license specified, setting license = 'unknown'
Deleting META.yml
Creating META.yml
Creating foo-0.01
[EMAIL PROTECTED]:~/dev/foo$ ls foo-0.01/
Build.PL MANIFEST META.yml
[EMAIL PROTECTED]:~/dev/foo$
No Makefile.PL. :-( Could "create_makefile_pl => passthrough" Become
the default, and a new option, "create_makefile_pl => skip" be created to
satisfy those who wish to screw over legacy users? :)
- Tyler
