Jerry D. Hedden wrote: > In perltodo.pod, it reads: > Bundle dual life modules in ext/ > For maintenance (and branch merging) reasons, it would be useful to move > some architecture-independent dual-life modules from lib/ to ext/, if > this has no negative impact on the build of perl itself. > > However, we need to make sure that they are still installed in > architecture-independent directories by "make install". Nicholas Clark <nick@ccl4.org> wrote: > Oh. I might have failed on that bit. Yes, I just noticed this. It seems that anything that is built 'nonxs' from ext/ is placed in architecture-DEPENDENT dirs. This is very bad because arch libs come first in @INC. That means that upgrading such modules from CPAN will not work correctly because the upgraded code will be masked by the old code. This needs to be fixed. Can anyone give some insight as to where to start looking?Thread Next