[imp] Repost: Upgrading

[Eric Rostetter]

Quoting Phil Dibowitz <phil@ipom.com>:

> Are there any issues in upgrading from 3.0 to 3.1. There are no metions of
> upgrading in docs/INSTALL, or anywhere else I can find.

You would need to upgrade all the config files to match your old setup while
including any new additions.
 
> So would:
> 
> cp -R imp-3.1/* /path/to/horde/imp/
> 
> be a good way to do it?

Not really.  You would end up with a mixture of old and new...

> Will I loose config changes? Are 3.0 configs
> compatible with 3.1? What else would I need to do.

The new config files come as *.dist files, so they will not overwrite your
old config files.  But you will then need to update your old files somehow.
See the list archives for info.  There are some scripts in the archives/cvs
which help to merge the new config with the old.

I don't remember there being any issues from IMP 3.0 to IMP 3.1 besides
config files, but my memory could be wrong.

My favorite way to update is to install the new version along side to the
old.  Then configure it and test it.  When done configuring and testing it,
rename the old one to imp.old and the new one to imp, and voila!  I'd
upgrade Horde at the same time if you aren't running the latest Horde, 
although this is totally optional and not required.

> Thanks,
> --
> Phil Dibowitz                             phil@ipom.com

-- 
Eric Rostetter
The Department of Physics
The University of Texas at Austin

"TAD (Technology Attachment Disorder) is an unshakable, impractical devotion
to a brand, platform, product line, or programming language. It's relatively
harmless among the rank and file, but when management is afflicted the damage
can be measured in dollars. It's also contagious -- someone with sufficient
political clout can infect an entire organization."

--"Enterprise Strategies" columnist Tom Yager.