* Jeffrey <jeffreykeg...@jeffreykegler.com> [2010-03-22 00:50]: > @Aristotle: Your two one-syllable answers were very useful.
I realised afterwards that the mail reads somewhat gruff rather than (as intended) amused. Sorry. > An obstacle for me was that Module::Build's actual behavior > seems to contradict the documentation in Module::Build::API, > which says of 'build_requires' that > > "Modules listed in this section are necessary to build and > install the given module, but are not necessary for regular > usage of it." > > Read literally, that says that any module necessary for regular > usage should never be listed under 'build_requires'. As far as > I can tell the actual behavior of Module::Build would be more > in accord with the following: > > "Modules listed in this section are necessary to build and > install the given module. If a listed module is necessary for > regular usage as well as the build and install, the listed > module also needs to be specified using the 'requires' > argument." Right, it’s simply that one of these is for code that runs in normal operation and the other is for the code that runs during installation. If a module is needed at both times, it should be listed in both sections. It’s odd that adding to `build_requires` fixes any problem though. Older CPAN toolchains only understand `requires`, and many modules list all their dependencies there and do not even have a distinct `build_requires` list. To my knowledge those modules work fine. So your problem is a bit of a mystery. Hmm. (Nevertheless, your solution is the correct thing to do, so don’t go reverting it.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
