Conference smurf::buildhelp

2348.0. "Will there be a tool for making .mods for test patches ? AND" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Jun 19 1996 22:58

Date Of Receipt: 	19-JUN-1996 18:12:15.25
From: 	FLUME::"katz@minsrv.zk3.dec.com" "19-Jun-1996 1750"
To: 	odehelp@zk3.dec.com
CC: 	useg_reng@mudrat.zk3.dec.com, metsch@zk3.dec.com
Subj: 	Will there be a tool for making .mods for test patches ? AND

will it start by pulling .o's off of guru where the latest and 
greatest (as in tested) .o's exist, rather than pulling them out of
the current pool (which includes some fixes that still need 
integration testing).
I would expect that a .mod will require a set of files. If I make
a change to one of those files (X), then the .mod (x) that should be 
produced should have X from my sandbox, and the rest (a) if a 
patched version exists on guru, then use it, or (b) take it from
the original ssb kit. 
Then further, one must be aware that due to intersection of files 
for a patch, that it may be necessary to put out multiple .mods when 
a single .mod is being changed. This is because if file X had a 
connection to file Y (in .mod y) then their .mods are married from 
then on. One cannot afford to take .mod x without .mod y

Without this consideration, using .mods will be a support nightmare. 

Thanks for listening,
Charlie Katz