Bug 93299

Description Ted Chiasson 2005-04-29 13:42:17 EDT

If you use the PDE packaging tool to do multiple packages using the same source 
zips it is very inefficient.
The tool grabs all the zips required from the maps file, and by default it 
unzips them into a temp dir.
It then does all the packaging based on that tree.
Unfortunately, at the end of the build, it deletes the tree.
The delete command is in the last few lines of the generated "assemble.xml", I 
believe.
It is definitely in one of the generated files, and so it is impossible to 
remove the delete command.
If you could request "no delete" then all the packaging could be done off the 
same unzipped tree.
In cases where we are packaging hundreds of megs, this is significant.
Improved behaviour would allow the user to specify where to start the packaging.
i.e. 1)start at beginning, do the fetch, unzip, package
2) zips already fetched by previous build, just unzip and package
3) use the tree that the previous build laid out, just package these features 
for me

I am using releng.basebuilder to do these packaging tasks headlessly in a 
production environment.

opened after talking to Pascal
Thanks.