Yes, the CPAN autobundle functionality is still current and is a somewhat viable option. Autobundle also bundles core modules, which means that you need some cleanup when moving between Perl versions.

Great. Thanks

Once autobundle has been used to make a bundle for my current workstation, how does one distinguish the core modules from the rest? And, with cpan, cpanm, and/or cpanp, are dependencies handled resiliently? (i.e. if a package depends on another that just happens to occur after it in the list of modules to install, does it handle that in a manner similar to how make handles targets that depend on other targets in the makefile? yes, I have a background in C++ programming, and in using Gnu make to handle building some of my more interesting programs)

Thanks

Ted

Module::CoreList tells you what module came with which version of Perl.

As far as I rememeber, a bundle is installed in order. But then, CPAN will not do the work again if it already has done it, so the order in the bundle does not really matter, at least for modules that correctly specify their prerequisites.

Update: s/Module::Corelist/Module::CoreList/

modules have been in core and been removed from core ;;; so cleanup could be problematic ... scandeps? :)