| Subject: | Running API in-process creates @INC conflicts |
I recently encountered one problem with the whole idea of running the
M::B API in-process, as opposed to shelling out for "perl Build.PL"...
If you use CPANPLUS to attempt multiple tests/installs and happen to
make use of the same class name for your custom derived M::B classes
(e.g. "MY::Build"), you get an @INC conflict; the module gets loaded
up for the -first- package you try to build and never gets reloaded on
any subsequent packages. Thus, any subsequent package tests/installs
you try to do end up using the custom M::B class from the first
package you built. Boom.