On 4 Aug 2006, at 14:04, Johan Vromans wrote:
Ken Williams <[EMAIL PROTECTED]> writes:
My intention when I added 'build_requires' to Module::Build was not
to let people avoid downloading & building those dependencies, but
rather to indicate that there was no runtime dependency, ...
For this to function properly, the 'build_requires' modules (and their
respecitve dependencies!) should all be downloaded and installed in a
temporary location (e.g., blib) and not be installed permanently.
I don't think that's the necessary conclusion. Personally I prefer
build requirements to be installed permanently - so I don't have to
build them repeatedly when multiple modules require the same build
requirements.
What build_requires does is enable different folk to make different
decisions depending on what their needs are.
Adrian
