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

28 lines
639 B
Makefile
Raw Normal View History

Update to 1.5.1 (The date below is corrected). Two patches are removed, those are now included in upstream patches/patch-Makefile.am patches/patch-Makefile.in ----------- 2013-06-08 Ben Elliston <bje@gnu.org> * DejaGnu 1.5.1 released. 2013-06-08 Ben Elliston <bje@gnu.org> * configure.ac (AC_INIT): Bump version to 1.5.1. * runtest.exp (frame_version): Likewise. * configure: Regenerate. * Makefile.in: Regenerate with automake 1.13. * aclocal.m4: Likewise.
2013-06-16 06:54:51 +02:00
# $NetBSD: Makefile,v 1.17 2013/06/16 04:54:51 mef Exp $
DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Beyond this, DejaGnu offers several advantages for testing: - The flexibility and consistency of the DejaGnu framework make it easy to write tests for any program. - DejaGnu provides a layer of abstraction which makes all tests (if correctly written) portable to any host or target where a program must be tested. For instance, a test for GDB can run (from any Unix based host) on any target architecture supported by DejaGnu. Currently DejaGnu runs tests on several single board computers, whose operating software ranges from just a boot monitor to a full-fledged, Unix-like realtime OS. - DejaGnu is written in expect, which in turn uses Tcl (Tool command language). The framework comprises two parts: the testing framework and the testsuites themselves. Tests are usually written in expect using Tcl.
2001-05-30 06:17:52 +02:00
#
Update to 1.5.1 (The date below is corrected). Two patches are removed, those are now included in upstream patches/patch-Makefile.am patches/patch-Makefile.in ----------- 2013-06-08 Ben Elliston <bje@gnu.org> * DejaGnu 1.5.1 released. 2013-06-08 Ben Elliston <bje@gnu.org> * configure.ac (AC_INIT): Bump version to 1.5.1. * runtest.exp (frame_version): Likewise. * configure: Regenerate. * Makefile.in: Regenerate with automake 1.13. * aclocal.m4: Likewise.
2013-06-16 06:54:51 +02:00
DISTNAME= dejagnu-1.5.1
DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Beyond this, DejaGnu offers several advantages for testing: - The flexibility and consistency of the DejaGnu framework make it easy to write tests for any program. - DejaGnu provides a layer of abstraction which makes all tests (if correctly written) portable to any host or target where a program must be tested. For instance, a test for GDB can run (from any Unix based host) on any target architecture supported by DejaGnu. Currently DejaGnu runs tests on several single board computers, whose operating software ranges from just a boot monitor to a full-fledged, Unix-like realtime OS. - DejaGnu is written in expect, which in turn uses Tcl (Tool command language). The framework comprises two parts: the testing framework and the testsuites themselves. Tests are usually written in expect using Tcl.
2001-05-30 06:17:52 +02:00
CATEGORIES= devel
MASTER_SITES= ${MASTER_SITE_GNU:=dejagnu/}
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Beyond this, DejaGnu offers several advantages for testing: - The flexibility and consistency of the DejaGnu framework make it easy to write tests for any program. - DejaGnu provides a layer of abstraction which makes all tests (if correctly written) portable to any host or target where a program must be tested. For instance, a test for GDB can run (from any Unix based host) on any target architecture supported by DejaGnu. Currently DejaGnu runs tests on several single board computers, whose operating software ranges from just a boot monitor to a full-fledged, Unix-like realtime OS. - DejaGnu is written in expect, which in turn uses Tcl (Tool command language). The framework comprises two parts: the testing framework and the testsuites themselves. Tests are usually written in expect using Tcl.
2001-05-30 06:17:52 +02:00
HOMEPAGE= http://www.gnu.org/software/dejagnu/dejagnu.html
COMMENT= TCL/Expect-based framework for regression testing
Bump dejagnu 1.4.4 to 1.5 ------------------------- patches/patch-ab Upstream now includes this change, removed. patches/patch-ac Doc generation has changed and doc directory does not exist any more, removed. patches/patch-Makefile.am *.exp files were execution bit set because of target name, patch added. has -SCRIPT string. Now correcting to -DATA patches/patch-Makefile.in Generated by automake-1.11.1 from Makefile.am, patch added. ------------------------- Changes since 1.4.4: 1. The runtest.1 man page has been brought up to date. 2. The Docbook/SGML documentation files were removed in favour of the Docbook/XML documentation. The Texinfo source for the Info pages is now automatically generated from the Docbook source. 3. The Makefile structure has been substantially simplified. There is now a single top-level Makefile.am. The use of recursive make has been eliminated. 4. lib/mondfe.exp and lib/xsh.exp have been removed. Users requiring these communication modes can still use the DejaGnu 1.4 branch or can contact dejagnu@gnu.org to discuss reinstating these files. 5. The configure script now ensures that Expect is installed and that it is linked against Tcl 8.3 or greater. 6. The runtest program now gracefully handles the possibility of the expect binary vanishing after DejaGnu has been installed (for example, by the user altering their PATH). 7. The user-visible utility procedures `absolute', `prune', `psource' and `slay' are deprecated and will be removed in the next release. If a testsuite uses any of these procedures, a copy of the procedure should be made and placed in the lib directory of the testsuite.
2013-06-10 03:09:48 +02:00
LICENSE= gnu-gpl-v3
DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Beyond this, DejaGnu offers several advantages for testing: - The flexibility and consistency of the DejaGnu framework make it easy to write tests for any program. - DejaGnu provides a layer of abstraction which makes all tests (if correctly written) portable to any host or target where a program must be tested. For instance, a test for GDB can run (from any Unix based host) on any target architecture supported by DejaGnu. Currently DejaGnu runs tests on several single board computers, whose operating software ranges from just a boot monitor to a full-fledged, Unix-like realtime OS. - DejaGnu is written in expect, which in turn uses Tcl (Tool command language). The framework comprises two parts: the testing framework and the testsuites themselves. Tests are usually written in expect using Tcl.
2001-05-30 06:17:52 +02:00
Back out previous commit, related to PR 37477. Only runtime dependency on 'expect' command included in lang/tcl-expect package. No need to buildlink to lang/tcl-expect.
2007-12-08 14:50:31 +01:00
DEPENDS+= tcl-expect>=5.32.1:../../lang/tcl-expect
DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Beyond this, DejaGnu offers several advantages for testing: - The flexibility and consistency of the DejaGnu framework make it easy to write tests for any program. - DejaGnu provides a layer of abstraction which makes all tests (if correctly written) portable to any host or target where a program must be tested. For instance, a test for GDB can run (from any Unix based host) on any target architecture supported by DejaGnu. Currently DejaGnu runs tests on several single board computers, whose operating software ranges from just a boot monitor to a full-fledged, Unix-like realtime OS. - DejaGnu is written in expect, which in turn uses Tcl (Tool command language). The framework comprises two parts: the testing framework and the testsuites themselves. Tests are usually written in expect using Tcl.
2001-05-30 06:17:52 +02:00
GNU_CONFIGURE= yes
Bump dejagnu 1.4.4 to 1.5 ------------------------- patches/patch-ab Upstream now includes this change, removed. patches/patch-ac Doc generation has changed and doc directory does not exist any more, removed. patches/patch-Makefile.am *.exp files were execution bit set because of target name, patch added. has -SCRIPT string. Now correcting to -DATA patches/patch-Makefile.in Generated by automake-1.11.1 from Makefile.am, patch added. ------------------------- Changes since 1.4.4: 1. The runtest.1 man page has been brought up to date. 2. The Docbook/SGML documentation files were removed in favour of the Docbook/XML documentation. The Texinfo source for the Info pages is now automatically generated from the Docbook source. 3. The Makefile structure has been substantially simplified. There is now a single top-level Makefile.am. The use of recursive make has been eliminated. 4. lib/mondfe.exp and lib/xsh.exp have been removed. Users requiring these communication modes can still use the DejaGnu 1.4 branch or can contact dejagnu@gnu.org to discuss reinstating these files. 5. The configure script now ensures that Expect is installed and that it is linked against Tcl 8.3 or greater. 6. The runtest program now gracefully handles the possibility of the expect binary vanishing after DejaGnu has been installed (for example, by the user altering their PATH). 7. The user-visible utility procedures `absolute', `prune', `psource' and `slay' are deprecated and will be removed in the next release. If a testsuite uses any of these procedures, a copy of the procedure should be made and placed in the lib directory of the testsuite.
2013-06-10 03:09:48 +02:00
INFO_FILES= yes
DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Beyond this, DejaGnu offers several advantages for testing: - The flexibility and consistency of the DejaGnu framework make it easy to write tests for any program. - DejaGnu provides a layer of abstraction which makes all tests (if correctly written) portable to any host or target where a program must be tested. For instance, a test for GDB can run (from any Unix based host) on any target architecture supported by DejaGnu. Currently DejaGnu runs tests on several single board computers, whose operating software ranges from just a boot monitor to a full-fledged, Unix-like realtime OS. - DejaGnu is written in expect, which in turn uses Tcl (Tool command language). The framework comprises two parts: the testing framework and the testsuites themselves. Tests are usually written in expect using Tcl.
2001-05-30 06:17:52 +02:00
Bump dejagnu 1.4.4 to 1.5 ------------------------- patches/patch-ab Upstream now includes this change, removed. patches/patch-ac Doc generation has changed and doc directory does not exist any more, removed. patches/patch-Makefile.am *.exp files were execution bit set because of target name, patch added. has -SCRIPT string. Now correcting to -DATA patches/patch-Makefile.in Generated by automake-1.11.1 from Makefile.am, patch added. ------------------------- Changes since 1.4.4: 1. The runtest.1 man page has been brought up to date. 2. The Docbook/SGML documentation files were removed in favour of the Docbook/XML documentation. The Texinfo source for the Info pages is now automatically generated from the Docbook source. 3. The Makefile structure has been substantially simplified. There is now a single top-level Makefile.am. The use of recursive make has been eliminated. 4. lib/mondfe.exp and lib/xsh.exp have been removed. Users requiring these communication modes can still use the DejaGnu 1.4 branch or can contact dejagnu@gnu.org to discuss reinstating these files. 5. The configure script now ensures that Expect is installed and that it is linked against Tcl 8.3 or greater. 6. The runtest program now gracefully handles the possibility of the expect binary vanishing after DejaGnu has been installed (for example, by the user altering their PATH). 7. The user-visible utility procedures `absolute', `prune', `psource' and `slay' are deprecated and will be removed in the next release. If a testsuite uses any of these procedures, a copy of the procedure should be made and placed in the lib directory of the testsuite.
2013-06-10 03:09:48 +02:00
CONFIGURE_ARGS+= --infodir=${PREFIX}/info
* destdir support * fix permission * install documentation. Bump PKGREVISION.
2007-12-08 14:54:34 +01:00
Bump dejagnu 1.4.4 to 1.5 ------------------------- patches/patch-ab Upstream now includes this change, removed. patches/patch-ac Doc generation has changed and doc directory does not exist any more, removed. patches/patch-Makefile.am *.exp files were execution bit set because of target name, patch added. has -SCRIPT string. Now correcting to -DATA patches/patch-Makefile.in Generated by automake-1.11.1 from Makefile.am, patch added. ------------------------- Changes since 1.4.4: 1. The runtest.1 man page has been brought up to date. 2. The Docbook/SGML documentation files were removed in favour of the Docbook/XML documentation. The Texinfo source for the Info pages is now automatically generated from the Docbook source. 3. The Makefile structure has been substantially simplified. There is now a single top-level Makefile.am. The use of recursive make has been eliminated. 4. lib/mondfe.exp and lib/xsh.exp have been removed. Users requiring these communication modes can still use the DejaGnu 1.4 branch or can contact dejagnu@gnu.org to discuss reinstating these files. 5. The configure script now ensures that Expect is installed and that it is linked against Tcl 8.3 or greater. 6. The runtest program now gracefully handles the possibility of the expect binary vanishing after DejaGnu has been installed (for example, by the user altering their PATH). 7. The user-visible utility procedures `absolute', `prune', `psource' and `slay' are deprecated and will be removed in the next release. If a testsuite uses any of these procedures, a copy of the procedure should be made and placed in the lib directory of the testsuite.
2013-06-10 03:09:48 +02:00
INSTALL_TARGET= install install-info
# c++ is necessary for make test
USE_LANGUAGES+= c c++
TEST_TARGET= check
TEST_ENV= PATH=/usr/bin:/bin:${PREFIX}/bin
* destdir support * fix permission * install documentation. Bump PKGREVISION.
2007-12-08 14:54:34 +01:00
DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Beyond this, DejaGnu offers several advantages for testing: - The flexibility and consistency of the DejaGnu framework make it easy to write tests for any program. - DejaGnu provides a layer of abstraction which makes all tests (if correctly written) portable to any host or target where a program must be tested. For instance, a test for GDB can run (from any Unix based host) on any target architecture supported by DejaGnu. Currently DejaGnu runs tests on several single board computers, whose operating software ranges from just a boot monitor to a full-fledged, Unix-like realtime OS. - DejaGnu is written in expect, which in turn uses Tcl (Tool command language). The framework comprises two parts: the testing framework and the testsuites themselves. Tests are usually written in expect using Tcl.
2001-05-30 06:17:52 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink