OK, after looking at this information, it seems like the much saner thing would be to adhere to the CPAN standard for packaging (e.g. using Module::Starter), and then do a local cpaninject, and use cpan to deploy all my (local) perl packages. This has the slight downside that perl will be "an end in itself". But then again, I'm not going to use perl as base libraries for other programs (e.g. GUI apps).

The basic issue seems to be mixing packaging systems, and the usual problems having two standards causes. Note, however, that there have been people doing auto RPM builds as early as 2003. I stumbled upon this guy's site...http://rpmpan.sourceforge.net/, in addition to the ref you gave.