> Date: Sat, 02 Jun 2007 04:02:59 +0200
> From: Roland Mainz <roland.mainz at nrubsig.org>
> Subject: Next /opt/SUNWspro/bin/lint party ... / was: Re: [osol-code] Re:
[Fwd: [ksh93-integration-discuss] ksh93-integration pre-reviewround"two"
(webrev
2007-05-14)]
> To: "Roger A. Faulkner" <Roger.Faulkner at sun.com>
> Cc: al at logical-approach.com, peter.memishian at sun.com, Mike.Kupfer at
> sun.com,
Rod.Evans at sun.com, opensolaris-code at opensolaris.org,
ksh93-integration-discuss at opensolaris.org, bart.smaalders at sun.com,
Craig.Mohrman at eng.sun.com, casper.dik at sun.com, stephen.hahn at sun.com
>
> > So the next time we have a lint party (we used to do them every
> > couple of years), we can easily identify the lint-dirty sources.
>
> What if the sources are externally maintained (e.g. "perl", "ksh93") ?
> Is there a procedure to say "... provide lint fixes to upstream..." ?
Well, we just punt on perl with this in the Makefile
(since no one at Sun will ever attempt to sanitize it):
# Perl is not lint-clean. Fake up a target.
lint:
@ $(ECHO) "usr/src/cmd/perl is not lint-clean: skipping"
@ $(TRUE)
As for ksh93, we'd have to invent the procedure.
I certainly hope that making the code lint-clean would be viewed
favorably by the community and that pushing such changes upstream
would be straightforward. Ditto for bug fixes (or have you fixed
the last bug in ksh93? :-) Won't happen for a while, at least.
Roger
