I've run into an issue with Module::Build that I haven't found an easy workaround for yet. We subclass Module::Build for the BioPerl core distribution (now on CPAN: http://search.cpan.org/~cjfields/BioPerl-1.6.0/) . We have several other optional smaller sub-distributions (BioPerl- db, BioPerl-run, etc) that are available separately via CPAN. All share the common 'Bio' module namespace.

Apparently, each distribution recreates Bio::ConfigData (they all use 'feature' or 'auto_feature'), which is causing problems with automated packaging:

https://bugzilla.redhat.com/show_bug.cgi?id=484495

We have several ways we could solve this (not install ConfigData, have separate customized ConfigData files for each distribution, or use one common Bio::ConfigData for all distributions). However I haven't found any documentation on how to prevent ConfigData installation or generate/reuse custom-named ConfigData files. Any help would be greatly appreciated.

chris

Reply via email to