Hi. It looks like that these days "recommends()" is not recommended by
the toolchain people as it prevents smooth installation/packaging by
prompts, and I don't think it's a good idea to add extra
"build_recommends" just for completeness, as plain "recommends" is
usually used as if it were "build_recommends". Thoughts?
On 2008-7-19 Sat 04:26:23, leegee@gmail.com wrote:
Show quoted text> Adam Kennedy via RT wrote:
> It'd be nice if the client had module X to run some tests,
> but it is not needed by the actual PM being installed.
>
> Use of module in tests is recommended, but not recquired,
> since those tests catch the missing-module error and then skip_all
if
Show quoted text> absent.
>
> build_requires
> [version 0.07]
>
> Modules listed in this section are necessary to build and
> install the given module, but are not necessary for
regular
Show quoted text> usage of it. This is actually an important distinction -
it
Show quoted text> allows for tighter control over the body of installed
modules,
Show quoted text> and facilitates correct dependency checking on binary/
packaged
Show quoted text> distributions of the module.
>
> build_recommends
> Modules listed in this section are recommended to run the
test
Show quoted text> included in the given distribution, but their abscence will
> not prevent
> the module's installation.
>
> Then maybe one day there could be an install option, "Install the n
> missing modules, recommended for testing?"
>
> Just a thought
>
> tia
> Lee
>
>