On Sat, 2002-06-01 at 11:24, Al Tobey wrote: > try out /usr/lib/rpm/cpanflute or /usr/lib/rpm/cpanflute2
Yeah, cpanflute and cpanflute2 are wonderful tools. > This should work for most any CPAN module. > The world is a happy place ... There are some minor vendor specific idiosyncrasy though. cpanflute* generate %file list using "find". Mandrake RPM Howto specifically discourages this. http://www.linux-mandrake.com/en/howtos/mdk-rpm/building.html#AEN267 Note that you should never use find to build a list of files to include but explicitely list all files (this'll show up bugs in new versions). There are also convention differences. For example, Mandrake tends to use %real_name for the name fo the module, whereas PLD uses %module. Also Mandrake's rpm macros include definitions of paths to binaries such as make, perl as %{__make} and %{__perl}. Another is that some times the specfiles generated need to be tweaked because of bugs in MakeMaker. For example, some makefile variables need to be explicitly overridden. With perl modules, the frequent offenders of this category are INSTALLMAN1DIR, INSTALLMAN3DIR, INSTALLSITEMAN1DIR, and INSTALLSITEMAN3DIR. There is a thread about this in May on the rpm mailing list. http://www.redhat.com/mailing-lists/rpm-list/msg06859.html The moral of the story is that while it's straight-forward to generate a rpm specfile for a CPAN module, it does take additional effort and understanding to make it conform to a specific distribution's conventions (if one so desires). Pete
