We want to clean up obsolete files before we start adding new stuff just in case we eventually add a file back in that has the same name as an obsolete file we're removing.
Sean put some notes in bugscape bug number 9941 that explain this further.
Comment on attachment 56031 [details] [diff] [review] For ns r=ssu
Attachment #56031 - Flags: review+
Comment on attachment 56033 [details] [diff] [review] for mozilla r=ssu
Attachment #56033 - Flags: review+
Why would we ever delete a file that we're just going to replace? I agree, though, that if we ever do such a silly thing then this order is much safer. sr=dveditz
The fix is checked in to mozilla and ns trunk. Just as a record of our thinking, it might be that a file witht he same name as an obsolete file we are deleting might get reintroduced and the odds are good that noone would catch the fact that it is being deleted. That is at least one scenerio under which we might do this silly thing. So this just plays it safe.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
verified code fixes-upgradecleanup before add dirs
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.