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

Document the need for many more automated tests.

Browse source
This commit is contained in:
schmonz 2013-03-26 15:08:53 +00:00
parent 162e744ca1
commit 26062d5a38
2 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
pkgtools/pkglint/README
View file

@ -1,7 +1,11 @@
$NetBSD: README,v 1.4 2006/02/28 23:32:47 rillig Exp $
$NetBSD: README,v 1.5 2013/03/26 15:08:53 schmonz Exp $
== Current problems ==
There are finally some automated tests that document a few intended
and actual behaviors. There is still plenty of poorly expressed
code not yet under test and therefore not yet safe to refactor.
The current pkglint architecture will not scale much further. What is
needed next are parsers for nested, non-context-free languages (make(1),
sh(1), sed(1)). The parsers should be able to recognize partial

4
pkgtools/pkglint/TODO
View file

@ -1,8 +1,10 @@
$NetBSD: TODO,v 1.74 2012/09/15 10:55:15 wiz Exp $
$NetBSD: TODO,v 1.75 2013/03/26 15:08:53 schmonz Exp $
Please add your own entries at the bottom of this file. If possible,
include the name of an example package where a warning should occur.
* When you understand some behavior of the code, document it by
adding automated tests to pkglint.t!
* fix false positive warnings
* warn about the use of ${WRKDIR:=...}, as this construct should only
be used with lists.