id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
311	create static configuration files for feisty meow build config	Fred T. Hamster		"the first phase of the build process should be writing the 
appropriate values into a loadable config file;
in every OS this should be true.

then in windows, we simply pull in the configured file!

this can be redone as needed to set the configs back up.

way better than all that awful code in the clam file itself
trying to get the paths calculated.

so, we're talking about a clam config file mainly?  we can source it like we do other clam files?
"	refactoring	new	minor		feistymeow-scripts			build, config