id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
3	build variables and yeti vars leaking out of scripts	Fred T. Hamster	Fred T. Hamster	there's a set of variables: PARM_0 etc that seem to be set by the build variables.  clean that out.  and this is probably a problem in many of our config scripts, setting variables for one use that then linger around.  clean up this stuff.  easily done by making more functions and having those variables be local to the functions called to set up stuff.	bug	closed	minor		feistymeow-scripts		wontfix