pkgsrc/pkgtools/pkglint
rillig f09c8701b9 If one of the NO_*_ON_* variables contains something other that
${RESTRICTED}, print the variable name in the warning message.

While here, added an explanation for the warning.
2008-01-01 20:44:29 +00:00
..
files If one of the NO_*_ON_* variables contains something other that 2008-01-01 20:44:29 +00:00
DESCR Replaced the DESCR from the year 2001 with a current one, since pkglint has 2005-12-01 04:05:36 +00:00
Makefile Updated pkglint to 4.81. 2007-12-22 11:21:47 +00:00
PLIST 4.15.1: Fix PLIST (hi Roland!). 2005-05-18 21:06:58 +00:00
README The rant on Perl has moved to the pkglint book. 2006-02-28 23:32:47 +00:00
TODO Cleaned up the TODO list from things I don't find worth implementing. 2007-09-10 07:38:46 +00:00

$NetBSD: README,v 1.4 2006/02/28 23:32:47 rillig Exp $

== Current problems ==

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.