pkgsrc/pkgtools/pkglint
rillig ea4dea64cd Added the ability to resolve simple variable references of the form
${VARNAME} into their values.

This was intended to fix the false positive warnings about missing
distinfo files, but it cannot handle database/ruby-gdbm for example,
because _RUBY_VER_MAJOR uses pattern substitution. Run pkglint with
-Dtrace,misc and look for resolve_var to see what happens up to now.
2009-07-17 20:06:22 +00:00
..
files Added the ability to resolve simple variable references of the form 2009-07-17 20:06:22 +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 Remove redundant NO_CHECKSUM and EXTRACT_ONLY definitions. 2009-04-09 00:48:06 +00:00
PLIST Remove @dirrm entries from PLISTs 2009-06-14 18:10:40 +00:00
README The rant on Perl has moved to the pkglint book. 2006-02-28 23:32:47 +00:00
TODO take case-insensitive filesystems into account. 2009-04-05 13:05:16 +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.