quick applicatons upgrade ques..

[Chris Fadrowski]

When upgrading MirrorUX, Glance, etc... to the new application releases, is it a good idea to swremove the exisiting apps first or can you just install over them without problems..

(obviously you wouldn't want to swremove MirrorUX) but what is the general rule for these types of app upgrades.

I do know that i swremove "ignite" when upgrading to a new version. just found it to be cleaner.

[Steven E. Protter · Accepted solution]

In general, you do not need to swremove first. I've had some exceptions with Ignite 3.x, but that was probably my own misfiring pea brain molecules.

SEP

[Chris Fadrowski]

thanks

just wanted to double check. I never have with apps, but always wondered if i had orphaned files out there.

[A. Clay Stephenson]

Each product varies but the "general rule" if such a thing exists, is to remove all the cumulative patches for a product and then remove the product itself. Things like configuration files are almost always left in place by the swremove's. There are, of course, exceptions.

In almost all cases, the upgrade procedure is reasonably well-documented so you really need to approach this on a product-by-product basis --- and sometimes, the rules even change between releases of a given product.

I would say one of the most common oversights is failing to look for and install any patches/updates for the new product. Just because you have the latest, greatest release of a product does not mean that there are not already patches out there for it.

My firmest rule is either create a "lifeboat" via dd or do a make_tape_recovery beforehand. That way, you won't need it -- it's one of God's little jokes.