At 10:51 AM -0500 2/18/05, Dave Greenwood wrote: >I plan to add several additional CPAN modules. Is there an advantage to >building them into perl as opposed to adding or upgrading them later? I'm >thinking of the question in @CONFIGURE about which modules to build into >perl. If there is an advantage, how do I answer the question? Do I >need to re-enter all the default modules plus my additional modules? Or >do I just enter the additional modules?
The question in configure.com is based on reading the manifest to get a list of all the extensions included as part of the Perl core. It's not a particularly useful question now that the list is so long since it would be difficult or impossible to edit such a long list manually. Whether you want to integrate additional modules into the core before building or install them later is really up to you. If you are planning to build a source kit that you will build many times, possibly in different places, then it may be worth the extra effort to integrate the non-core modules first. If you are just trying to get an installed Perl that has all the goodies you want, then I would just install the core and then build and install each module of interest. The only impact on an installed Perl of adding modules after the initial build is that the modules will reside under perl_root:[lib.site_perl] rather than perl_root:[lib]. Note that an installed Perl can be zipped up or placed in a backup saveset and moved anywhere you like, including to other systems of the same architecture and the same or later VMS version. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
