pkgsrc/pkgtools/pkglint
rillig f139df9027 Fixed variable type of PYTHON_VERSIONED_DEPENDENCIES, so that build-time
and run-time dependencies can be specified without pkglint warnings.
2014-10-08 19:15:16 +00:00
..
files Fixed variable type of PYTHON_VERSIONED_DEPENDENCIES, so that build-time 2014-10-08 19:15:16 +00:00
DESCR
Makefile Allow '+' in another place checking for package names. Needed e.g. for gtk2+. 2014-09-08 12:03:32 +00:00
PLIST
README Document the need for many more automated tests. 2013-03-26 15:08:53 +00:00
TODO - Added check for unused license files 2013-10-12 18:09:59 +00:00

$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.