Front page | perl.perl5.porters |
Postings from April 2003
Craig Berry wrote: !It must be a holdover from before installperl worked on VMS (which I !think means pre-5.5.3) so a cleaned-up build directory had to !function as an installed Perl. Probably all the copying of pod/ to !lib/pod is in there for the same reason. If we could get rid of !these two things, we would probably shrink descrip_mms.template by !25% and have less maintenance to do as new .h and .pod files are !added. It's looking to me like the benefits probably outweigh the !risks; are you ready to start swinging the axe? I am fairly certain that your explanation of the pod/... to lib/pod/... copying was originally done for the reason you cite (installperl not working). Unfortunately I am uncertain if that is the sole explanation for the .h file handling. The non working installperl seems like a good explanation but I just don't know if it is the only explanation. I certainly agree that both the pods and the .h files are a maintenance headache. I'd like to help out if I can (gzipped tar kits help me out a lot of course). Do you want to retain the ability to run the source tree as your PERL_ROOT or would it be OK to break that? Is this destined for 5.8.1 or later? Thanks. Peter PrymmerThread Previous | Thread Next