Log message:
Substantially re-work the NetBSD_All.mk which started out as a naive
copy of the Linux.mk. Builds on amd64 now.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
Mark packages that don't or might probably not have staged installation.

Log message:
Syncing distinfo with patches.

Log message:
Restore the patches to what I had before. The distributed files have
MSDOS line endings, and apparently there is no way to work around
pkglint's warning

<3>wip/jsl > pkglint -e
ERROR: patches/patch-ab:5: The hunk header must not end with a CR character.
        
        The MacOS X patch utility cannot handle these.
        
ERROR: patches/patch-ac:5: The hunk header must not end with a CR character.
        
        The MacOS X patch utility cannot handle these.
        
2 errors and 0 warnings found.
<3>wip/jsl >

-- at least, pkgdiff(1) does not implement any.

Log message:
Import jsl-0.3.0

Many JavaScript implementations do not warn against questionable
coding practices. Yes, that's nice for the site that "works best with
Internet Explorer" (designed with templates, scripted with snippets
copied from forums). But it's a nightmare when you actually want to
write quality, maintainable code.

That's where JavaScript Lint comes in. With JavaScript Lint, you can
check all your JavaScript source code for common mistakes without
actually running the script or opening the web page.

JavaScript Lint holds an advantage over competing lints because it is
based on the JavaScript engine for the Firefox browser. This provides
a robust framework that can not only check JavaScript syntax but also
examine the coding techniques used in the script and warn against
questionable practices.