I'm curious about how CPAN handles bundles. What makes a bundle a bundle? Is it just any module starting with the name "Bundle"?
The bundle contains a .pm file with a bunch of pod containing the names of modules that are members of the bundle. In order to install those member modules, CPAN has to take the actual bundle .pm file and stick it in @INC and then do the bundle voo-doo. How does that work? Can anyone explain that voo-doo?
I can make my own custom bundles, by creating the .pm file with the appropriate pod, sticking it in "cpan_home/Bundle/" and then running "i Bundle::name_of_bundle".
I'm asking all this because I'm trying to include custom bundles in a CPAN::Mini with CPAN::Mini::Inject, but it's not working. I think I need to understand the under-the-hood mechanisms of CPAN in regards to bundles in order to figure this out.
This post is the third in a series: CPAN and Site Modules and CPAN::Mini::Inject and Bundles.
Update: Success!! See CPAN::Mini::Inject Discoveries.
In reply to Bundle basics by pileofrogs
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |