I just built an RPM from perl-ldap-0.30.tar.gz, using cpanflute2 from the RPM::Specfile module. Because the tarball's name doesn't match the usual CPAN format (eg. Net-LDAP-0.30.tar.gz), the resulting RPM is named perl-perl-ldap. I imagine other CPAN-related utilities would have similar problems with it. Any particular reason the perl-ldap module uses that name? Just history? Apart from inertia, is there any strong reason not to change it to fit the pattern used by other modules?

This isn't a big deal; it just leads to odd names in generated packages or extra steps required to normalize them for inclusion in distros.

(For those interested in building the RPM, use "cpanflute2 --buildall perl-ldap-0.30.tar.gz".)

Reply via email to