pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2002-11-25	Update dejagnu to 1.4.3nb1.	kristerw	3	-2/+16
	Fix bug that made tests organized in deep directory structures (e.g. the gcc testsuite) be run multiple times.
2002-09-27	Update devel/dejagnu to version 1.4.3.	kristerw	4	-21/+24
	Changes since 1.4.1 include: - New XML output option, so test results can be loaded into a database. - Support for the KFAIL/KPASS (known failures). This is mostly oriented towards GDB testing. - New tutorial chapter. - Test case builds with either libstdc++-v3 (as used by gcc-3.0.x) or the older v2.(as used by gcc-2.95.x)
2002-08-01	Change MAINTAINER from tv at netbsd dot org to packages at netbsd dot org	jschauma	1	-2/+2
	after consulting with Todd. Any volunteers for any of these packages?
2001-11-01	Move pkg/ files into package's toplevel directory	zuntum	2	-1/+1

2001-05-31	MD5--, SHA1++ (MD4 and SHA2?)	wiz	1	-3/+3

2001-05-30	Fix thinko in @dirrm syntax.	tv	1	-5/+5

2001-05-30	DejaGnu is a framework for testing other programs. Its purpose is to	tv	5	-0/+207
	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.