The <company>-perl-Module-Build solution works well for my simple scenario. But I don't think it scales to more than two perl's on one machine. What if I have the system perl (perl-5.8.x), developer perl 1 (perl-5.10) and developer perl 2 (perl 5.12). What is a good way to deal with this? I think taking the RPM naming approach to its logical conclusion means I end up with three packages for the same module, one for each version of perl. Is this what people actually do? I can see the advantage but it seems like a hell of a lot of duplication of effort.