Hello MB list of a month ago,
On Jul 31, 2007, at 4:47 PM, David Golden wrote:
On 7/31/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
Had there been a discussion of something like this?
I think META.yml should have test_requires, and possibly also
test_recommends.
Particularly, since we have ACTION_retest(), we should ensure that
everything is available.
I thought that was what "build_requires" was for. I seem to recall
some discussion that it was supposed to be everything up to actual
installation and that further granularity with uncertain benefit, but
a lot of toolchain support changes, wasn't a priority.
For the reasons Eric mentions, it would indeed be nice to split
test_requires off from build_requires.
The problem is that we've always defined testing as part of
building. If we now split someone's test prereqs into test_requires
and stop listing them in build_requires, then any tool that doesn't
know about test_requires will miss that prereq and tests will fail.
So if we did make this split, people would have to keep listing such
prereqs in build_requires too. I suspect that would become confusing.
-Ken
