2 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] (no subject)
FromSent OnAttachments
Allan DukatAug 14, 2008 1:45 pm 
Sam VarshavchikAug 14, 2008 6:12 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] (no subject)Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Aug 14, 2008 6:12:12 pm
List:net.sourceforge.lists.courier-sqwebmail

Allan Dukat writes:

Hi all

For the time being, I do not have a spare computer for developing purpurse, so I would like to install version 5.2.2 of SqWebMail in parallel whith my production version, 5.2.0, on my production server.

SqWebMail version, 5.2.0 is compiled whith this configure command:

./configure \ --without-gzip \ --enable-https \ --enable-hardtimeout=36000 \ --enable-softtimeout=7200 \ --enable-cgibindir=/usr/local/apache2/cgi-bin \ --enable-imagedir=/usr/local/apache2/icons \ --enable-imageurl=/icons \ --enable-mimetypes=/usr/local/apache2/conf/mime.types \ --with-ispell=/usr/bin/aspell \ --disable-autorenamesent

Which options du I have to change, and which do I need to add, in order to be able to test SqWebMail version 5.2.2, without any disturbance of my customers use of version 5.2.0, if possible.

I am looking forward to your answer. Thanks in advance.

You need to add a new --prefix option, and provide different --enable-cgibindir, --enable-imagedir, and --enable-imageurl=/icons options.

--enable-cgibindir isn't strictly necessary, all that does is set where 'make install' puts the cgi-bin stub. You can, alternative, rename your existing binary in cgi-bin, and let your new build install its own sqwebmail binary into cgi-bin, that's a valid alternative.

The other two options are related, and must be set accordingly.