In an environment where there are multiple versions of Perl installed (for the moment lets just say two: the system perl and the latest, stable perl...I'll call this last one the developer perl) what is the recommended way to build and RPM package CPAN modules? Should the system perl and the developer perl share modules (and therefore packages for modules)? What about modules that are compiled and (may) need to be compiled against a specific perl? So far the only solution I've come up with is an entirely different naming scheme for the developer perl's RPMs: the system perl's RPMs are named f.e. perl-Module-Build whereas I'd name the developer perl's module <company>-perl-Module-Build. This doesn't seem like the best solution but I have been unable to find any solutions using Google and the like.
So what recommendations are there for a) proper way to build modules for the above situation and b) the naming scheme for the RPMs.