pkglint(1)

changeset: 2046:2522cde7adc2
tag: tip
user: Tim Foster
date: Thu Aug 26 13:11:20 2010 +1200
description:
13536 We need a way to audit one or more packages
15860 publication api needs auditing phase
15862 pkglint tool needed aid in package creation and auditing
16828 ProgressTracker should make it easier for others to interleave output
16875 we should be able to execute tests directly from the source
16800 pkglint should allow signature actions in obsolete and renamed manifests

we now have pkglint(1), a tool that can check package metadata for common errors before publishing. We never really had an equivalent for SVR4 packages, although many have written scripts to do so. The pkglint man page documents how the tool works.

Out of the box, the below checks are performed on manifests, either retrieved from a repository, or passed as local files on the command line. It’s also pretty easy to extend pkglint(1) with your own checks (details in the man page) If you think there might be something missing out of this default list, do please let me know.

Over the coming weeks, I’ll be addressing some additional bugs and RFEs for pkglint. Once we’re sure it’s stable, I hope to start working with the right folks to see if we can get pkglint(1) runs performed on their gates during their builds.

Many thanks to everyone who helped code review and provide feedback – it was very much appreciated!