If you have set up WikkiTikkiTavi in a common location (see TaviInstructions#Suggestions), automatic upgrading is a breeze.

For example, consider the following setup. You or the site administrator have installed 'Tavi in /usr/local/lib/tavi/tavi-0.21, and created a symbolic link to that directory named /usr/local/lib/tavi/tavi-current.

If all instances of the script reference the version in /usr/local/lib/tavi/tavi-current, then you can upgrade by installing 'Tavi into /usr/local/lib/tavi/tavi-0.nn, and then redirecting /usr/local/lib/tavi/tavi-current to point to that location.

Any scripts that absolutely depend on running a back-level version of 'Tavi (which should be unlikely) can under this scheme reference the /usr/local/bin/tavi/tavi-0.nn versions if necessary.

If you're really brave (not recommended) you can run a periodic cron job to refresh your local version of 'Tavi from the CVS repository on SourceForge (see TaviCVS).

More likely, you will periodically visit this website or the [download page] to see if there's a new release, and install it as outlined above.

It would also be possible to write a cron job to periodically poll http://dl.sourceforge.net/tavi/ and download a newer version if one exists. (You might want to exclude any that include "alpha" or "beta" in their title.) Anyone who wishes to contribute such an example script is welcome to post it right here on this page.

Return to TaviDocumentation.