pkgsrc

History

schmonz 3745e6657e Respond to wiz's code review: * In test, match the "make makesum" warning more loosely. * In test, find packages to run against in $PKGSRCDIR explicitly. * Bump version. This is the last commit in a set developed for my "Rehabilitating pkglint" talk at pkgsrcCon 2013. Reviewed-at-pkgsrcCon-and-approved-during-the-freeze-by: wiz		2013-03-26 15:11:36 +00:00
..
files	Respond to wiz's code review:	2013-03-26 15:11:36 +00:00
DESCR
Makefile	Respond to wiz's code review:	2013-03-26 15:11:36 +00:00
PLIST	Remove @dirrm entries from PLISTs	2009-06-14 18:10:40 +00:00
README	Document the need for many more automated tests.	2013-03-26 15:08:53 +00:00
TODO	Document the need for many more automated tests.	2013-03-26 15:08:53 +00:00

README

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