[ic] Upgrade procedure

[Gert van der Spoel]

> -----Original Message-----
> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
> users-bounces at icdevgroup.org] On Behalf Of Peter
> Sent: Sunday, June 14, 2009 7:51 AM
> To: interchange-users at icdevgroup.org
> Subject: Re: [ic] Upgrade procedure
> 
> On 06/13/2009 04:33 PM, Grant wrote:
> > I'd like to perform a safe upgrade from a 5.5 nightly to 5.6.  Should
> > this be sufficient:
> >
> > # tar -cvzf ic.tar.gz /usr/local/ic
> > # su - interchange
> > $ cd /new/ic/source
> > $ ./configure
> > $ exit
> > # cd /new/ic/source
> > # make install
> 
> No, my usual upgrade procedure is this:
> As unprivileged user:
> 
> ~$ tar.cvzf ic.tar.gz # use the proper name of the tarball here
> 
> ~$ cd interchange # use the correct name of the directory that the
> tarball created here
> 
> 
> ~/interchange$ /path/to/your/perl Makefile.PL # and answer prompt about
> where to put interchange


My different approach at this point is that I put the new interchange in a
separate directory, ie:
/opt/interchange-5.7.1/


> ~/interchange$ make
> 
> ~/interchange$ make test
> 
> ~/interchange$ su
> 
> At this point make a backup of your current interchange install.
> 
> ~/interchange# make install
> 

In the most simple case you now have an interchange.cfg file to copy over to
the new tree.
When you have done various changes to your core, I'd suggest to create a
'build' script that you can run over the latest tree to apply your patches
to the tree ... 

There would be a symlink pointing to the latest version you are using
ie /opt/interchange/  pointing to /opt/interchange-5.4.0

Once you did all your custom fixes and followed further steps regarding the
UPGRADE (changes to pages, local usertags, databases etc). Then you can
switch around your symlink and restart.

If things do not look like they are working well, you can switch back your
symlink and restart and you're back on your previous install.


> At this point you need to read the UPGRADE file (actually you should
> have already read it) and make any tweaks or adjustments listed in
> there
> for your particular version upgrade.
> 
> Also at this point you should compile a new vlink or tlink or whatever
> you use.  See the compile_link program in the ic/bin directory for more
> info, "./compile_link --help" gives you the arguments to use.
> 
> Cross fingers and restart interchange.
> 
> Check the error logs to make sure that startup is clean.
> 
> Check your sites to make sure they all still work as expected.
> 
> Note that if you've made any custom tweaks to the interchange core then
> the onus is on you to make sure they are still there and re-tweak if
> necessary.
> 
> 
> Peter
> 
> _______________________________________________
> interchange-users mailing list
> interchange-users at icdevgroup.org
> http://www.icdevgroup.org/mailman/listinfo/interchange-users