Ken Williams <ken@xxxxxxxxxxxxx> wrote:
> If we did that, we'd screw over people who are already maintaining
> their Makefile.PL separately by hand.
OK... but if they are doing that, the Makefile.PL will be in their
*build* directory already... as far as I understand, our Makefile.PL only
needs to be generated in the *dist* directory.
The current behaviour is to not create a Makefile.PL during
"./Build", only create it when "distdir" is run. However, the "distdir"
action creates "Makefile.PL" in the current directory and then copies it
over.
The generated Makefile.PL's first line clearly says "auto-generated
by Module::Build::Compat"... soooo if somebody was maintaining a Makefile.PL
manually, we could easily auto-detect that by checking for the presence of
that line. Maybe echo a Big Fat Warning on the distdir action as well, if
they havent explicitly set "create_makefile_pl => skip".
Do you think that would make everybody happy?
> Not everybody has as many modules to maintain as we do, Tyler. =)
Hah, you're way ahead of me on that one. ;) What scares me is how
many *nearly* complete modules i have sitting in my CVS tree that need just
a few more changes to be ready... each night I load up one and add a few
more methods/test cases/etc and think that's the night it's going to be
ready to release just to find a whole days' worth of work I hadn't
considered...
- Tyler
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
