Add software updates package source restrictions or warnings
When a software updates package is created, the given path is cleared of any existing content. This is very destructive if an incorrect path is given. One of several things should happen:
1. Restrict the location of software updates packages if another package is using the same folder or any folder below.
2. Warn if additional content is detected in the given path for a software updates package.
3. Not clear additional content from software updates packages source locations.
We recently ran into this with a co-worker making documentation and put in the root path for all of our packages (software updates, osd, apps, etc) and all of our source folders were deleted.
Example: source for package A is \\cm01\packages\PackageA and source for a new software update package was set to \\cm01\packages, results are PackageA folder is gone as well as any other folders.