kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/atf/Makefile

35 lines
887 B
Makefile
Raw Normal View History

Update to ATF 0.16: Experimental version released on July 10th, 2012. * Added a --enable-tools flag to configure to request the build of the deprecated ATF tools, whose build is now disabled by default. In order to continue running tests, you should migrate to Kyua instead of enabling the build of the deprecated tools. The kyua-atf-compat package provides transitional compatibility versions of atf-run and atf-report built on top of Kyua. * Tweaked the ATF_TEST_CASE macro of atf-c++ so that the compiler can detect defined but unused test cases. * PR bin/45859: Fixed some XSLT bugs that resulted in the tc-time and tp-time XML tags leaking into the generated HTML file. Also improved the CSS file slightly to correct alignment and color issues with the timestamps column. * Optimized atf-c++/macros.hpp so that GNU G++ consumes less memory during compilation with GNU G++. * Flipped the default to building shared libraries for atf-c and atf-c++, and started versioning them. As a side-effect, this removes the --enable-unstable-shared flag from configure that appears to not work any more (under NetBSD). Additionally, some distributions require the use of shared libraries for proper dependency tracking (e.g. Fedora), so it is better if we do the right versioning upstream. * Project hosting moved from an adhoc solution (custom web site and Monotone repository) to Google Code (standard wiki and Git). ATF now lives in a subcomponent of the Kyua project.
2012-07-11 00:02:59 +02:00
# $NetBSD: Makefile,v 1.21 2012/07/10 22:02:59 jmmv Exp $
Initial import of atf-0.1: The Automated Testing Framework (ATF) is a collection of libraries and utilities designed to ease unattended application testing in the hands of developers and end users of a specific piece of software. As regards developers, ATF provides the necessary means to easily create test suites composed of multiple test programs, which in turn are a collection of test cases. It also attempts to simplify the debugging of problems when these test cases detect an error by providing as much information as possible about the failure. As regards users, it simplifies the process of running the test suites and, in special, encourages end users to run them often: they do not need to have source trees around nor any other development tools installed to be able to certify that a given piece of software works on their machine as advertised. Yes, these are (part of) the results of my SoC 2007 project :-)
2007-08-20 13:59:17 +02:00
#
Split the ATF libraries into their own devel/atf-libs package. This change adds a new atf-libs package that provides the libatf-c, libatf-c++ and libatf-sh libraries by themselves, without any of the ATF runtime tools. The atf package has been modified to only install the runtime utilities (atf-run and atf-report being the major ones) and depend on atf-libs. The purpose of this change is to allow packages that install tests to depend on a lighter-weight package, and to allow the addition of the upcoming kyua-atf-compat package. The latter will be a package that provides atf-run and atf-report replacements based on kyua-cli, and therefore will conflict with the atf tools (but not the libraries). While doing this, fix the pkgconfig overrides and ensure that we use the right version of the ATF libraries given that disabling shared library building appears to have been broken, possibly for a while.
2012-07-01 17:27:43 +02:00
.include "Makefile.common"
Initial import of atf-0.1: The Automated Testing Framework (ATF) is a collection of libraries and utilities designed to ease unattended application testing in the hands of developers and end users of a specific piece of software. As regards developers, ATF provides the necessary means to easily create test suites composed of multiple test programs, which in turn are a collection of test cases. It also attempts to simplify the debugging of problems when these test cases detect an error by providing as much information as possible about the failure. As regards users, it simplifies the process of running the test suites and, in special, encourages end users to run them often: they do not need to have source trees around nor any other development tools installed to be able to certify that a given piece of software works on their machine as advertised. Yes, these are (part of) the results of my SoC 2007 project :-)
2007-08-20 13:59:17 +02:00
Update to ATF 0.16: Experimental version released on July 10th, 2012. * Added a --enable-tools flag to configure to request the build of the deprecated ATF tools, whose build is now disabled by default. In order to continue running tests, you should migrate to Kyua instead of enabling the build of the deprecated tools. The kyua-atf-compat package provides transitional compatibility versions of atf-run and atf-report built on top of Kyua. * Tweaked the ATF_TEST_CASE macro of atf-c++ so that the compiler can detect defined but unused test cases. * PR bin/45859: Fixed some XSLT bugs that resulted in the tc-time and tp-time XML tags leaking into the generated HTML file. Also improved the CSS file slightly to correct alignment and color issues with the timestamps column. * Optimized atf-c++/macros.hpp so that GNU G++ consumes less memory during compilation with GNU G++. * Flipped the default to building shared libraries for atf-c and atf-c++, and started versioning them. As a side-effect, this removes the --enable-unstable-shared flag from configure that appears to not work any more (under NetBSD). Additionally, some distributions require the use of shared libraries for proper dependency tracking (e.g. Fedora), so it is better if we do the right versioning upstream. * Project hosting moved from an adhoc solution (custom web site and Monotone repository) to Google Code (standard wiki and Git). ATF now lives in a subcomponent of the Kyua project.
2012-07-11 00:02:59 +02:00
COMMENT:= ${COMMENT} - Runtime tools (deprecated; use kyua-cli)
Initial import of atf-0.1: The Automated Testing Framework (ATF) is a collection of libraries and utilities designed to ease unattended application testing in the hands of developers and end users of a specific piece of software. As regards developers, ATF provides the necessary means to easily create test suites composed of multiple test programs, which in turn are a collection of test cases. It also attempts to simplify the debugging of problems when these test cases detect an error by providing as much information as possible about the failure. As regards users, it simplifies the process of running the test suites and, in special, encourages end users to run them often: they do not need to have source trees around nor any other development tools installed to be able to certify that a given piece of software works on their machine as advertised. Yes, these are (part of) the results of my SoC 2007 project :-)
2007-08-20 13:59:17 +02:00
Update to ATF 0.16: Experimental version released on July 10th, 2012. * Added a --enable-tools flag to configure to request the build of the deprecated ATF tools, whose build is now disabled by default. In order to continue running tests, you should migrate to Kyua instead of enabling the build of the deprecated tools. The kyua-atf-compat package provides transitional compatibility versions of atf-run and atf-report built on top of Kyua. * Tweaked the ATF_TEST_CASE macro of atf-c++ so that the compiler can detect defined but unused test cases. * PR bin/45859: Fixed some XSLT bugs that resulted in the tc-time and tp-time XML tags leaking into the generated HTML file. Also improved the CSS file slightly to correct alignment and color issues with the timestamps column. * Optimized atf-c++/macros.hpp so that GNU G++ consumes less memory during compilation with GNU G++. * Flipped the default to building shared libraries for atf-c and atf-c++, and started versioning them. As a side-effect, this removes the --enable-unstable-shared flag from configure that appears to not work any more (under NetBSD). Additionally, some distributions require the use of shared libraries for proper dependency tracking (e.g. Fedora), so it is better if we do the right versioning upstream. * Project hosting moved from an adhoc solution (custom web site and Monotone repository) to Google Code (standard wiki and Git). ATF now lives in a subcomponent of the Kyua project.
2012-07-11 00:02:59 +02:00
CONFIGURE_ARGS+= --enable-tools
Initial import of atf-0.1: The Automated Testing Framework (ATF) is a collection of libraries and utilities designed to ease unattended application testing in the hands of developers and end users of a specific piece of software. As regards developers, ATF provides the necessary means to easily create test suites composed of multiple test programs, which in turn are a collection of test cases. It also attempts to simplify the debugging of problems when these test cases detect an error by providing as much information as possible about the failure. As regards users, it simplifies the process of running the test suites and, in special, encourages end users to run them often: they do not need to have source trees around nor any other development tools installed to be able to certify that a given piece of software works on their machine as advertised. Yes, these are (part of) the results of my SoC 2007 project :-)
2007-08-20 13:59:17 +02:00
Update to 0.3: * Added XML output support to atf-report. This is accompanied by a DTD for the format's structure and sample XSLT/CSS files to post-process this output and convert it to a plain HTML report. * Changed atf-run to add system information to the report it generates. This is currently used by atf-report's XML output only, and is later printed in the HTML reports in a nice and useful summary table. The user and system administrator are allowed to tune this feature by means of hooks. * Removed the test cases' 'isolated' property. This was intended to avoid touching the file system at all when running the related test case, but this has not been true for a long while: some control files are unconditionally required for several purposes, and we cannot easily get rid of them. This way we remove several critical and delicate pieces of code. * Improved atf-report's CSV output format to include information about test programs too. * Fixed the tests that used atf-compile to not require this tool as a helper. Avoids systems without build-time utilities to skip many tests that could otherwise be run. (E.g. NetBSD without the comp.tgz set installed.) * Many general cleanups: Fixed many pieces of code marked as ugly and/or incomplete.
2007-11-11 22:46:41 +01:00
XML_ENTRIES= public "-//NetBSD//DTD ATF Tests Results 0.1//EN" \
${PREFIX}/share/xml/atf/tests-results.dtd
Split the ATF libraries into their own devel/atf-libs package. This change adds a new atf-libs package that provides the libatf-c, libatf-c++ and libatf-sh libraries by themselves, without any of the ATF runtime tools. The atf package has been modified to only install the runtime utilities (atf-run and atf-report being the major ones) and depend on atf-libs. The purpose of this change is to allow packages that install tests to depend on a lighter-weight package, and to allow the addition of the upcoming kyua-atf-compat package. The latter will be a package that provides atf-run and atf-report replacements based on kyua-cli, and therefore will conflict with the atf tools (but not the libraries). While doing this, fix the pkgconfig overrides and ensure that we use the right version of the ATF libraries given that disabling shared library building appears to have been broken, possibly for a while.
2012-07-01 17:27:43 +02:00
post-install:
.for file in bin/atf-sh \
include/ \
lib/ \
libexec/ \
${PKGMANDIR}/man1/atf-check.1 \
${PKGMANDIR}/man1/atf-sh.1 \
${PKGMANDIR}/man1/atf-test-program.1 \
${PKGMANDIR}/man3/ \
${PKGMANDIR}/man4/ \
share/aclocal/ \
share/atf/libatf-sh.subr \
tests/atf/atf-c++ \
tests/atf/atf-c \
tests/atf/atf-sh \
tests/atf/test-programs
rm -rf ${DESTDIR}${PREFIX}/${file}
.endfor
.include "../../devel/atf-libs/buildlink3.mk"
Update to 0.3: * Added XML output support to atf-report. This is accompanied by a DTD for the format's structure and sample XSLT/CSS files to post-process this output and convert it to a plain HTML report. * Changed atf-run to add system information to the report it generates. This is currently used by atf-report's XML output only, and is later printed in the HTML reports in a nice and useful summary table. The user and system administrator are allowed to tune this feature by means of hooks. * Removed the test cases' 'isolated' property. This was intended to avoid touching the file system at all when running the related test case, but this has not been true for a long while: some control files are unconditionally required for several purposes, and we cannot easily get rid of them. This way we remove several critical and delicate pieces of code. * Improved atf-report's CSV output format to include information about test programs too. * Fixed the tests that used atf-compile to not require this tool as a helper. Avoids systems without build-time utilities to skip many tests that could otherwise be run. (E.g. NetBSD without the comp.tgz set installed.) * Many general cleanups: Fixed many pieces of code marked as ugly and/or incomplete.
2007-11-11 22:46:41 +01:00
.include "../../textproc/xmlcatmgr/catalogs.mk"
Initial import of atf-0.1: The Automated Testing Framework (ATF) is a collection of libraries and utilities designed to ease unattended application testing in the hands of developers and end users of a specific piece of software. As regards developers, ATF provides the necessary means to easily create test suites composed of multiple test programs, which in turn are a collection of test cases. It also attempts to simplify the debugging of problems when these test cases detect an error by providing as much information as possible about the failure. As regards users, it simplifies the process of running the test suites and, in special, encourages end users to run them often: they do not need to have source trees around nor any other development tools installed to be able to certify that a given piece of software works on their machine as advertised. Yes, these are (part of) the results of my SoC 2007 project :-)
2007-08-20 13:59:17 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink