However, when I go to the zm-1.21.2/scripts directory, the zmupdate.pl has a .z extension (Usually this means gzipped but its actually not in this case).from version 1.19.5 you can use the zmupdate.pl script to do all the updating for you, this will include all the database changes plus any other tweaks necessary to upgrade to the latest version. To use it you should type
zmupdate.pl –version=<previous version> [--user=<db user> --pass=<db password>]
where ‘previous version’ relates to the version of ZM you are upgrading from, 1.19.4 for example. All updates from that versions onwards will be applied
rwxrwxr-x 1 zm zm 12696 Jun 23 01:39 zmupdate.pl.z
Is this because I have not run ./configure yet?
Can I copy the "configure.in" from my 1.21.1 install so I don't have to answer all the configuration questions again (and just run zmconfig.pl -noi)?
What happens if you install a newer version from RPM, will your old settings be reset to default?
It may be a good idea to have ZM store its configuration somewhere, and then have a "make upgrade" option that basically just compiles and installs the new binaries, and performs any database upgrades. I see there is a /usr/local/etc/zm.conf which contains some information like the db username and password...perhaps it could contain all of the configuration items, and the update script could get the values from there.
Note that I had no problem figuring out how to upgrade, I'm just trying to look from the perspective of someone who does not have a lot of experience with this sort of thing. I would suggest adding an "Upgrading" section to the readme, or a seperate README-upgrade.txt/html to make it easier for people to apply Zm updates.