Skip Menu |

This queue is for tickets about the ExtUtils-ModuleMaker CPAN distribution.

Report information
The Basics
Id: 11536
Status: resolved
Worked: 10 min
Priority: 0/
Queue: ExtUtils-ModuleMaker

People
Owner: jkeenan [...] cpan.org
Requestors: dalgoda [...] ix.netcom.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)



Subject: PL_FILES no longer works the same way with 6.25_0x
EU::MM's handling of PL_FILES changed between 6.25 and 6.25_01. It used to be that it would result in something like this: nexus@thune[6:22pm]src/MP3-Tag/MP3-Tag-0.94(526) grep data_pod Makefile.PL Makefile Makefile.PL: 'PL_FILES' => {'data_pod.PL'=>'ID3v2-Data.pod'}, Makefile:# PL_FILES => { data_pod.PL=>q[ID3v2-Data.pod] } Makefile:ID3v2-Data.pod :: data_pod.PL Makefile: $(PERLRUNINST) data_pod.PL ID3v2-Data.pod That is, the script to run could expect the output file as a parameter. Now it does: nexus@thune[6:23pm]src/MP3-Tag/MP3-Tag-0.94(530) grep data_pod Makefile.PL Makefile Makefile.PL: 'PL_FILES' => {'data_pod.PL'=>'ID3v2-Data.pod'}, Makefile:# PL_FILES => { data_pod.PL=>q[ID3v2-Data.pod] } Makefile:ID3v2-Data.pod :: data_pod.PL pm_to_blib.ts Makefile: $(PERLRUNINST) data_pod.PL While this change keeps within the spirit of the documentation (it never explicitly stated that would be passed as a parameter), it's possible that some users have come to expect that capability. For example, MP3-Tag-0.94 on cpan is such a package. Is this change intentional or accidental?
It was a bug introduced somewhere in the 6.25_X alphas. 6.27 fixed it.
From: JKEENAN
[guest - Wed Feb 16 21:28:49 2005]: Show quoted text
> EU::MM's handling of PL_FILES changed between 6.25 and 6.25_01. > > It used to be that it would result in something like this: > > nexus@thune[6:22pm]src/MP3-Tag/MP3-Tag-0.94(526) grep data_pod > Makefile.PL Makefile > Makefile.PL: 'PL_FILES' => {'data_pod.PL'=>'ID3v2- > Data.pod'}, > Makefile:# PL_FILES => { data_pod.PL=>q[ID3v2-Data.pod] } > Makefile:ID3v2-Data.pod :: data_pod.PL > Makefile: $(PERLRUNINST) data_pod.PL ID3v2-Data.pod > > That is, the script to run could expect the output file as a > parameter. > > Now it does: > nexus@thune[6:23pm]src/MP3-Tag/MP3-Tag-0.94(530) grep data_pod > Makefile.PL Makefile > Makefile.PL: 'PL_FILES' => {'data_pod.PL'=>'ID3v2- > Data.pod'}, > Makefile:# PL_FILES => { data_pod.PL=>q[ID3v2-Data.pod] } > Makefile:ID3v2-Data.pod :: data_pod.PL pm_to_blib.ts > Makefile: $(PERLRUNINST) data_pod.PL > > > While this change keeps within the spirit of the documentation (it > never explicitly stated that would be passed as a parameter), it's > possible that some users have come to expect that capability. For > example, MP3-Tag-0.94 on cpan is such a package. > > Is this change intentional or accidental?
This bug report was misfiled. It refers to ExtUtils::MakeMaker (and has received a reply from the maintainer of that module), not to ExtUtils::ModuleMaker (for which I have assumed maintenance).
See comment posted; the original bug was misfiled.