Hello!
My reason for this post is to gather info so that I can convince my software packagers to follow what I feel is the best way to update existing software resources. When a new version of software is issue from the vendor, I would download the latest version, import the software as a new software release and have the detection rules and other components be generated automatically for the first time.
My software packager wants to update an existing software resource, let's say Adobe Reader X to Adobe Reader XI by changing the UNC path to the location of the new files, manually changing the detection rule data, manually changing command line info and any other components related to Reader X that now have to be updated to Reader XI.
I'm of the mindset that when there is a new version (Adobe Reader 9, X, XI, e.t.c.) that a NEW software release should be created and not just update one over and over again. Please help me to provide a convincing argument as to why this percieved "extra work" is better overall.
A few reasons that I can come up with revolve around GUID creation. Each new software resource/release gets a new GUID created for it. So just opening up the same software resource each time and updating with a new version does not change the software release GUID. This may cause issues. Also, if the deployment of the latest software fails/bombs/e.t.c. then it would be more work to go back and change to the previous version.
Any others?
