04612c3d27
Up to now, all files whose names started with "patch-" were considered patch files. This was wrong, since e.g. devel/patch also has distfiles with the same naming pattern. |
||
---|---|---|
.. | ||
files | ||
DESCR | ||
Makefile | ||
PLIST | ||
README | ||
TODO |
$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 structures, as well as structures containing foreign parts. This is because most of pkgsrc is heavily based on preprocessors: - The .if and .for directives in Makefiles are preprocessed by make(1) before building dependencies and shell commands out of the remaining text. - make(1) assembles shell commands from literal text and variables like ${PKGNAME}. - Shell commands often use dynamic evaluation of variables. All this makes enhancing pkglint non-trivial. If you know of any academic papers that might be of help in this case, please tell me. The pkglint source code is much too big for a single file.