[csw-maintainers] GAR sanity check for a double variable assignment in build descriptions

[Ben Walton]

Excerpts from Sebastian Kayser's message of Wed Mar 18 17:43:40 -0400 2009:
> Mhh, what about a perl/*sh script along the lines of checkpkg that reads
> the build Makefile, searches all the = assignments and bails out or
> warns when hitting an assignment with a LHS that had been seen before?
> 
> This script could be invoked as part of the GAR build process.

That's pretty heavy weight for this and would still be error prone
(eg: what if you wrap it in and if statement for some bizarre
reason).  It would be nice if gmake had a --warn-redefined-variables
option (it already has a --warn-undefined-variables)...I suspect it
doesn't as it could get quite noisy, especially with something like
GAR that may redefine things already.

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20090318/062b8d94/attachment-0001.asc>