kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/p5-Test-Kwalitee/Makefile

31 lines
1.1 KiB
Makefile
Raw Normal View History

Recursive bump for perl5-5.28.0
2018-08-22 11:43:40 +02:00
# $NetBSD: Makefile,v 1.19 2018/08/22 09:44:46 wiz Exp $
Import p5-Test-Kwalitee version 1.01. Kwalitee is an automatically-measurable gauge of how good your software is. That's very different from quality, which a computer really can't measure in a general sense. (If you can, you've solved a hard problem in computer science.) In the world of the CPAN, the CPANTS project (CPAN Testing Service; also a funny acronym on its own) measures Kwalitee with several metrics. If you plan to release a distribution to the CPAN -- or even within your own organization -- testing its Kwalitee before creating a release can help you improve your quality as well. Test::Kwalitee and a short test file will do this for you automatically.
2008-10-31 01:36:19 +01:00
p5-Test-Kwalitee: update to 1.27. 1.27 2017-11-05 18:45:40Z - make taint test TODO when version.pm is not current (see RT#118087)
2017-11-08 21:46:46 +01:00
DISTNAME= Test-Kwalitee-1.27
Import p5-Test-Kwalitee version 1.01. Kwalitee is an automatically-measurable gauge of how good your software is. That's very different from quality, which a computer really can't measure in a general sense. (If you can, you've solved a hard problem in computer science.) In the world of the CPAN, the CPANTS project (CPAN Testing Service; also a funny acronym on its own) measures Kwalitee with several metrics. If you plan to release a distribution to the CPAN -- or even within your own organization -- testing its Kwalitee before creating a release can help you improve your quality as well. Test::Kwalitee and a short test file will do this for you automatically.
2008-10-31 01:36:19 +01:00
PKGNAME= p5-${DISTNAME}
Recursive bump for perl5-5.28.0
2018-08-22 11:43:40 +02:00
PKGREVISION= 1
Import p5-Test-Kwalitee version 1.01. Kwalitee is an automatically-measurable gauge of how good your software is. That's very different from quality, which a computer really can't measure in a general sense. (If you can, you've solved a hard problem in computer science.) In the world of the CPAN, the CPANTS project (CPAN Testing Service; also a funny acronym on its own) measures Kwalitee with several metrics. If you plan to release a distribution to the CPAN -- or even within your own organization -- testing its Kwalitee before creating a release can help you improve your quality as well. Test::Kwalitee and a short test file will do this for you automatically.
2008-10-31 01:36:19 +01:00
CATEGORIES= devel perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=Test/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://search.cpan.org/dist/Test-Kwalitee/
COMMENT= Perl5 module to test the Kwalitee of a distribution
Update to 1.14 Add missing DEPENDS Add LICENSE Upstream changes: 1.14 2013-09-04 01:38:29Z (Karen Etheridge) - updated inaccurate test prereq 1.13 2013-08-21 20:03:31Z (Karen Etheridge) - added missing abstract for kwalitee-metrics script - no longer issuing a warning if the test is running from xt/ (see v1.10) 1.12 2013-08-01 16:09:47 PDT-0700 (Karen Etheridge) - adjusted tests to compensate for changes made in Module::CPANTS::Analyse 0.88/0.90_01 1.11 2013-07-29 17:27:36 PDT-0700 (Karen Etheridge) - added missing kwalitee-metrics executable to the distribution 1.10 2013-07-28 17:18:31 PDT-0700 (Karen Etheridge) - we now issue a warning if running when neither AUTHOR_TESTING or RELEASE_TESTING environment variables or set - test level adjusted, so location of failing test is correct - include a script to dump all metrics ("kwalitee-metrics") 1.09 2013-07-18 10:34:33 PDT-0700 (Karen Etheridge) - the has_test_pod, has_test_pod_coverage tests have been removed - they are classified as 'extra', and have been largely considered to be a bad idea anyway (these are often shipped as, and ought to be, in xt/) - the extractable test has been removed, as it does nothing in dists before there is a tarball present - new tests have been added: all standard kwalitee tests that can be run on a bare distribution without a tarball 1.08 2013-07-15 17:59:47 PDT-0700 (Karen Etheridge) - documentation fixed to reflect what indicators are actually available - metric names are no longer hardcoded, so Module::CPANTS::Analyse has more freedom to add and remove metrics 1.07 2013-06-28 12:22:00 PDT-0700 (Karen Etheridge) - now the indicators are run in the exact order they are returned from Module::CPANTS::Kwalitee::*, as some tests depend on the results of earlier tests (charsbar) - synopsis updated to recommend a better way to run this module, ensuring that it is not run by cpantesters or at installation time - we no longer create a function in our namespace for every metric we are going to test -- this should not break anyone, as these subs were never documented as part of the public API 1.06 2013-05-13 14:15:33 PDT-0700 (Karen Etheridge) - restore previous behaviour of plan()ing in import, to unbreak some dists that didn't follow the docs (which in this case is ok since it's a horrible idea for a Test module to plan itself anyway) (v1.05) - more diagnostic data is printed when a test fails (RT#85107) 1.05 2013-05-12 17:17:32 PDT-0700 (Karen Etheridge) - more rigorous testing of output; (in order to make this possible) now we do END { done_testing } instead of planning a test count 1.04 2013-04-28 08:55:17 PDT-0700 (Karen Etheridge) - re-release with bumped developer prereqs to depend on a higher version of Test::More for t/00-compile.t and t/00-check-deps.t (RT#84900) 1.03 2013-04-27 05:49:31 PDT-0700 (Karen Etheridge) - fixed documentation to refer to the proper names of Kwalitee tests (RT#24506) (thanks, Gavin Sherlock!) - cleaned up partially-botched distribution metadata and README 1.02 2013-03-31 14:58:52 PDT-0700 (Karen Etheridge) - no operational changes - re-releasing under new management via github and Dist::Zilla
2013-09-08 03:45:49 +02:00
LICENSE= ${PERL5_LICENSE}
Import p5-Test-Kwalitee version 1.01. Kwalitee is an automatically-measurable gauge of how good your software is. That's very different from quality, which a computer really can't measure in a general sense. (If you can, you've solved a hard problem in computer science.) In the world of the CPAN, the CPANTS project (CPAN Testing Service; also a funny acronym on its own) measures Kwalitee with several metrics. If you plan to release a distribution to the CPAN -- or even within your own organization -- testing its Kwalitee before creating a release can help you improve your quality as well. Test::Kwalitee and a short test file will do this for you automatically.
2008-10-31 01:36:19 +01:00
Update to 1.14 Add missing DEPENDS Add LICENSE Upstream changes: 1.14 2013-09-04 01:38:29Z (Karen Etheridge) - updated inaccurate test prereq 1.13 2013-08-21 20:03:31Z (Karen Etheridge) - added missing abstract for kwalitee-metrics script - no longer issuing a warning if the test is running from xt/ (see v1.10) 1.12 2013-08-01 16:09:47 PDT-0700 (Karen Etheridge) - adjusted tests to compensate for changes made in Module::CPANTS::Analyse 0.88/0.90_01 1.11 2013-07-29 17:27:36 PDT-0700 (Karen Etheridge) - added missing kwalitee-metrics executable to the distribution 1.10 2013-07-28 17:18:31 PDT-0700 (Karen Etheridge) - we now issue a warning if running when neither AUTHOR_TESTING or RELEASE_TESTING environment variables or set - test level adjusted, so location of failing test is correct - include a script to dump all metrics ("kwalitee-metrics") 1.09 2013-07-18 10:34:33 PDT-0700 (Karen Etheridge) - the has_test_pod, has_test_pod_coverage tests have been removed - they are classified as 'extra', and have been largely considered to be a bad idea anyway (these are often shipped as, and ought to be, in xt/) - the extractable test has been removed, as it does nothing in dists before there is a tarball present - new tests have been added: all standard kwalitee tests that can be run on a bare distribution without a tarball 1.08 2013-07-15 17:59:47 PDT-0700 (Karen Etheridge) - documentation fixed to reflect what indicators are actually available - metric names are no longer hardcoded, so Module::CPANTS::Analyse has more freedom to add and remove metrics 1.07 2013-06-28 12:22:00 PDT-0700 (Karen Etheridge) - now the indicators are run in the exact order they are returned from Module::CPANTS::Kwalitee::*, as some tests depend on the results of earlier tests (charsbar) - synopsis updated to recommend a better way to run this module, ensuring that it is not run by cpantesters or at installation time - we no longer create a function in our namespace for every metric we are going to test -- this should not break anyone, as these subs were never documented as part of the public API 1.06 2013-05-13 14:15:33 PDT-0700 (Karen Etheridge) - restore previous behaviour of plan()ing in import, to unbreak some dists that didn't follow the docs (which in this case is ok since it's a horrible idea for a Test module to plan itself anyway) (v1.05) - more diagnostic data is printed when a test fails (RT#85107) 1.05 2013-05-12 17:17:32 PDT-0700 (Karen Etheridge) - more rigorous testing of output; (in order to make this possible) now we do END { done_testing } instead of planning a test count 1.04 2013-04-28 08:55:17 PDT-0700 (Karen Etheridge) - re-release with bumped developer prereqs to depend on a higher version of Test::More for t/00-compile.t and t/00-check-deps.t (RT#84900) 1.03 2013-04-27 05:49:31 PDT-0700 (Karen Etheridge) - fixed documentation to refer to the proper names of Kwalitee tests (RT#24506) (thanks, Gavin Sherlock!) - cleaned up partially-botched distribution metadata and README 1.02 2013-03-31 14:58:52 PDT-0700 (Karen Etheridge) - no operational changes - re-releasing under new management via github and Dist::Zilla
2013-09-08 03:45:49 +02:00
DEPENDS+= p5-Module-CPANTS-Analyse>=0.82:../../devel/p5-Module-CPANTS-Analyse
DEPENDS+= p5-Test-Warnings>=0:../../devel/p5-Test-Warnings
DEPENDS+= p5-CPAN-Meta-Check>=0:../../devel/p5-CPAN-Meta-Check
Add following lines for make test DEPENDS+= p5-namespace-clean-[0-9]*:../../devel/p5-namespace-clean # for make test BUILD_DEPENDS+= p5-Test-Deep-[0-9]*:../../devel/p5-Test-Deep BUILD_DEPENDS+= p5-Archive-Zip-[0-9]*:../../archivers/p5-Archive-Zip BUILD_DEPENDS+= p5-File-Find-Object-[0-9]*:../../devel/p5-File-Find-Object BUILD_DEPENDS+= p5-Class-XSAccessor-[0-9]*:../../devel/p5-Class-XSAccessor BUILD_DEPENDS+= p5-JSON-MaybeXS-[0-9]*:../../converters/p5-JSON-MaybeXS
2015-08-23 00:39:23 +02:00
DEPENDS+= p5-namespace-clean-[0-9]*:../../devel/p5-namespace-clean
# for make test
BUILD_DEPENDS+= p5-Test-Deep-[0-9]*:../../devel/p5-Test-Deep
BUILD_DEPENDS+= p5-Archive-Zip-[0-9]*:../../archivers/p5-Archive-Zip
BUILD_DEPENDS+= p5-File-Find-Object-[0-9]*:../../devel/p5-File-Find-Object
BUILD_DEPENDS+= p5-Class-XSAccessor-[0-9]*:../../devel/p5-Class-XSAccessor
BUILD_DEPENDS+= p5-JSON-MaybeXS-[0-9]*:../../converters/p5-JSON-MaybeXS
Import p5-Test-Kwalitee version 1.01. Kwalitee is an automatically-measurable gauge of how good your software is. That's very different from quality, which a computer really can't measure in a general sense. (If you can, you've solved a hard problem in computer science.) In the world of the CPAN, the CPANTS project (CPAN Testing Service; also a funny acronym on its own) measures Kwalitee with several metrics. If you plan to release a distribution to the CPAN -- or even within your own organization -- testing its Kwalitee before creating a release can help you improve your quality as well. Test::Kwalitee and a short test file will do this for you automatically.
2008-10-31 01:36:19 +01:00
USE_LANGUAGES= # empty
PERL5_PACKLIST= auto/Test/Kwalitee/.packlist
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink