Re: [hylafax-users] Upgrading to Hylafax+

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Michael Hallager wrote:
> 1. In a nutshell what is involved please?
>   

If you use RPM then it's probably as easy as:

 rpm -Uvh hylafax-5.2.1-*rpm
 faxsetup

If you're upgrading from source, then the usual:

 tar xzvf hylafax-5.2.1.tar.gz
 cd hylafax-5.2.1
 ./configure && make && make install
 faxsetup

Really the only things that you need to watch out for are the e-mail 
templates that exist in hylafax.org 4.3.x/4.4.x versions but not in 
earlier versions and not in HylaFAX+.

If you're using e-mail templating then you'll need to convert them to 
the faxrcvd_mail() and notify_mail() approaches described here:

   http://hylafax.sourceforge.net/howto/tweaking.php#ss6.12

OR you'll need to copy out (and this probably won't be fun) the whole 
faxrcvd/notify and templating mechanisms from the 4.3.x/4.4.x version 
and use it as a faxrcvd.custom/notify.custom approach.

Chances are good that you're not using e-mail templates or you're not 
doing something so extravagant with the templating that it cannot be 
easily converted to the scripted approach in HylaFAX+.

> 2. What are the locations of all the Hylafax bits that I should be backing up?

You should always have a backup of everything on the whole system.

The upgrade procedure should not obliterate anything that would normally 
be customized.  HOWEVER, I would strongly advise you that if you do not 
have a backup of the whole system anyway, then you should at least back 
up your /var/spool/hylafax/etc directory.

Thanks,

Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*