-=| David Golden, Fri, Oct 09, 2009 at 07:45:22AM -0400 |=- > 07. Enhance granularity of prerequisites > > Proposal: > > Add "test_requires" distinct from "build_requires". (Adam Kennedy) > > This proposal is driven by the needs of the downstream distribution > packagers. At Oslo, they requested this separation to allow them to more > accurately package modules. I forget, however, the EXACT mechanism that > this change was driving downstream, and this MUST be clarified before we > add it. Adding a new dependency type simply because it looks like a good > idea isn't sufficient, we need to be absolutely sure that it does what the > downstream wants before we add it. > > [...] > > * Speaking from a Debian perspective, whether it is required for > testing or > for building, we include it as a Build dependency. We try to run as many > tests as possible (including author tests, though we prefer > AUTOMATED_TESTING to RELEASE_TESTING now). We would really consider > test_requires and build_requires equivalent. (jawnsy)
Speaking as part of the group that dedicates its time on packaging CPAN dists for Debian, I'd say that we don't make difference between 'building' and 'testing' as the later is always part of the former in the Debian package build. Separating the requirements for tests that aren't supposed to be run during normal package building would be useful. Something like "author_test_requires". In general, we try to run as much tests as possible, unles they are things like Critic tests, which can break with nre releases of Perl-Critic. Currently we try to fine-tune using environment variables, and this works as long as authors use them consistently. Having a separate dependency declaration for fargile tests may hopefuly help standartize the usage of environment variables to turn them on. -- dam
signature.asc
Description: Digital signature
