How can one installation package replace another without uninstalling and reinstalling?

Amy,

I am going to give you some additional food for thought.

The reason why it would be normally better (with some caveats) to uninstall the original module first, and then install the new version, is so that if the old version contained a file which is no longer there on the new package, the actual no longer needed file is removed. Otherwise it will stay there forever as other "Sugar Clubbers" correctly mentioned.

The caveats on why you would not uninstall a module at times are:

• if the module would uninstall any required data (there are options to not do that, but if they have not been activated, it could be disruptive)
• if the vendor that built the module let you know to not uninstall the module

Hope it helps thinking the overall deployment process through

Amy,

I am going to give you some additional food for thought.

The reason why it would be normally better (with some caveats) to uninstall the original module first, and then install the new version, is so that if the old version contained a file which is no longer there on the new package, the actual no longer needed file is removed. Otherwise it will stay there forever as other "Sugar Clubbers" correctly mentioned.

The caveats on why you would not uninstall a module at times are:

• if the module would uninstall any required data (there are options to not do that, but if they have not been activated, it could be disruptive)
• if the vendor that built the module let you know to not uninstall the module

Hope it helps thinking the overall deployment process through