Re: Why Makefile.PL uses uppercase extension?

I wonder why Makefile.PL uses uppercase extention 'PL'

For someone, such as myself, who likes to build modules the ol' fashioned manual way, even the capital 'M' is a PITA.
Wouldn't it be nice if you could just type perl makefile.pl

Well ... on Windows perl makefile.pl works fine. It's only the case-sensitive systems that barf at such commands.
I haven't tried it out, but I suspect that if the distro had a 'makefile.pl' instead of a 'Makefile.PL' then the automated cpan/cpanm-type installations would fail.
Has anybody tested that ?

Cheers,
Rob

Comment on Re: Why Makefile.PL uses uppercase extension? Select or Download Code

Replies are listed 'Best First'.
Re^2: Why Makefile.PL uses uppercase extension? by graff (Chancellor) on Dec 23, 2014 at 08:32 UTC
It's interesting that GitHub recently had to release a security patch for Windows and MacOSX, because the case-insensitive file systems on those OS's would allow a user's own 'git.config' to be overwritten when downloading a code distro from a malicious source (potentially allowing a remote user to run arbitrary commands on the victim's machine).	[reply]
Re^2: Why Makefile.PL uses uppercase extension? by Anonymous Monk on Dec 22, 2014 at 08:30 UTC
Has anybody tested that ? Well, if the file system is case insensitive, `makefile.pl` will work, but MakeMaker will install makefile.pl along with the .pm See Read more... (2 kB) Naturally it won't work on case sensitive filesystems	[reply] [d/l] [select]