[cc-ed to [EMAIL PROTECTED]] Hi Mike,
thank you for your email. Mike Castle wrote:
I'm still stuck with 5.6.1. But I'm upgrading to the latest EU::MM as I write this mail.I'm using perl-5.8.0 with the latest in ExtUtils-MakeMaker stuff.
That is very odd. I was using the 5.6.1 std makemaker plus pmake from CPAN to just "make dist". This is the recommended thing to do from the perlnewmod manpage IIRC.The way that Math-Project3D is being packaged is causing issues with the newer stuff. Basically, nothing gets copied into the blib directory and nothing gets installed.
[...]
Okay, I will fix that in all future distributions. I wonder, however whether this might break with old versions of the MakeMaker stuff and/or the CPAN module?The new standard seems to be to put all of the modules into a lib directory. So, a recommended layout for your packages might be something like: ./Makefile.PL ./changes ./test.pl ./readme ./lib ./lib/Math ./lib/Math/Project3D ./lib/Math/Project3D/Function.pm ./lib/Math/Project3D.pm That is: mkdir lib mv Math lib
I can't possibly. I am stuck on Win32, my nmake is very broken and I can't seem to fix it and pmake is a hack. I will, however, trust your advice and package future distributions the way you suggested.If you are using an older version of perl, I believe that simply upgrading to the most recent versions of the MakeMaker stuff should reproduce this problem.
Of course, I will. My knowledge of these issues is fairly limited as well, though. (Which is why I cc-ed the mail [EMAIL PROTECTED])I don't know enough about the modules stuff to know if this is a bug in the MakeMaker stuff, an incompatible change, or simply a more strict handling of an existing definition of how the stuff is supposed to be used. But since it is fairly easy to fix, I'm hoping you will consider changing how you package your modules.
All the best,
Steffen M�ller
