./pkgtools/pkglint, Verifier for NetBSD packages

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 5.6.8, Package name: pkglint-5.6.8, Maintainer: rillig

pkglint checks whether a pkgsrc package conforms to the various
conventions established over the years. It produces warnings, errors and
notes and, upon request, explains them.

Before importing a new package or making changes to an existing package,
pkglint should be run in the package's directory to check for common
errors.


Required to build:
[pkgtools/cwrappers] [lang/go111]

Master sites:


Version history: (Expand)


CVS history: (Expand)


   2018-12-03 00:12:43 by Roland Illig | Files touched by this commit (24) | Package updated
Log message:
pkgtools/pkglint: update to 5.6.8

Changes since 5.6.7:

In pkgsrc-wip, if the first line of a file contains an expanded CVS Id,
it is not an error but only a note that it should be an unexpanded CVS
Id. The autofix for this no longer inserts a new line but replaces the
existing line.

Several refactorings and small improvements to the existing diagnostics.
   2018-12-02 03:06:23 by Roland Illig | Files touched by this commit (2)
Log message:
pkgtools/pkglint: remove outdated files
   2018-12-02 02:57:48 by Roland Illig | Files touched by this commit (77) | Package updated
Log message:
pkgtools/pkglint: update to 5.6.7

Changes since 5.6.6:

User-defined variables that are not yet added to BUILD_DEFS are only
reported once per file.

Unnecessary space after variable names is only worth a note instead of
a warning. Example:

        MASTER_SITES =  https://cdn.example.org/

All variable names that are defined in the pkgsrc infrastructure are
assumed to be available to the package Makefiles. This reduces the
number of wrong "used but not defined" warnings, at the expense of

Variable names that are used in other variable names are checked
whether they are defined somewhere. Example:

        CFLAGS+=        ${CFLAGS.${PARAM}}      # PARAM is now checked

In SUBST_SED, when the pattern is s,@VAR@,${VAR}, or a slight variant
thereof, pkglint suggests to define SUBST_VARS instead, which frees the
package author from thinking about how to escape special characters and
is generally easier to read. Example:

        SUBST_SED.class=        s,@VAR@,${VAR:Q},

        SUBST_VARS.class=       VAR

Directives like .if !defined(...) are now handled the same whether or
not there is a space after before the (...).

The check for locally modified files now works independently of the
timezone.

As always, lots of refactorings have happened under the hood. Many small
bugs have been discovered and fixed accordingly.
   2018-11-11 21:55:23 by Roland Illig | Files touched by this commit (1)
Log message:
pkgtools/pkglint: make goyacc accessible to the build
   2018-11-10 12:45:29 by Roland Illig | Files touched by this commit (1)
Log message:
pkgtools/pkglint: fix build

go-package.mk needs to be included at the bottom of the package Makefile
since it defines several make targets that pkglint also defines.
   2018-11-10 12:42:23 by Roland Illig | Files touched by this commit (1)
Log message:
pkgtools/pkglint: don't access the internet during the build

Pkglint needs goyacc, which is provided by devel/go-tools. But that
packages pulls in a lot of dependencies that are not needed for pkglint.
This includes a Perl interpreter and various cryptography packages.

Instead, during build, pkglint installs the only needed tool of that
collection (goyacc).

Since go-package.mk assumes that each pkgsrc package only downloads and
installs a single project, but pkglint now needs two of them (goyacc and
pkglint), most parts of go-package.mk had to be copied here and
implemented directly.
   2018-11-10 12:41:40 by Roland Illig | Files touched by this commit (1)
Log message:
pkgtools/pkglint: don't access the internet during the build

Pkglint needs goyacc, which is provided by devel/go-tools. But that
packages pulls in a lot of dependencies that are not needed for pkglint.
This includes a Perl interpreter and various cryptography packages.

Instead, during build, pkglint installs the only needed tool of that
collection (goyacc).

Since go-package.mk assumes that each pkgsrc package only downloads and
installs a single project, but pkglint now needs two of them (goyacc and
pkglint), most parts of go-package.mk had to be copied here and
implemented directly.
   2018-11-08 20:41:32 by Roland Illig | Files touched by this commit (1)
Log message:
pkgtools/pkglint: fix build when PKGSRC_RUN_TEST is not set