On Aug 26, 2008, at 1:10 PM, Martin Joseph wrote:
>
> On Aug 26, 2008, at 5:12 AM, Rob Gillan wrote:
>
>> Hi,
>>
>> We've always found it best to move our callweaver (working) directory
>> to a backup, delete everything, then recompile. If it fails, you can
>> always move the working directory back. It's always good to have a
>> clean base to work from.
> I agree in concept, but it shouldn't be necessary to break your
> existing install in order to upgrade.
>
The problem is that CW building process needs another level of
abstraction for directory names. Right now the install directory is
the same as the run directory.
If CW build had two defines, one for RUN and one for INSTALL, then you
could build a fresh version into an INSTALL directory and when it is
all built you could RUN it from the run directory.
Here is an example. Say we have two basedirs, INSTALLBASE and RUNBASE.
We set them as follows:
INSTALLBASE = /usr/local/callweaver-1.2.0.4
RUNBASE = /usr/local/callweaver
Then if you already have the following:
/usr/local/callweaver (symlink to -> /usr/local/callweaver-1.2.0.2)
/usr/local/callweaver-1.2.0.2
After the build you get:
/usr/local/callweaver-1.2.0.2
/usr/local/callweaver (symlink to -> /usr/local/callweaver-1.2.0.2)
/usr/local/callweaver-1.2.0.4
And when you are ready to try, you shutdown cw, delete and repoint
symlink to new build:
/usr/local/callweaver-1.2.0.2
/usr/local/callweaver-1.2.0.4
/usr/local/callweaver (symlink to -> /usr/local/callweaver-1.2.0.4)
and start cw. CW will know to run from the RUNBASE which is where the
symlink is pointing to. If cw doesn't work or has some problems, you
can always go back to the previous version, or whichever since you can
keep as many as you want.
So would this be a big deal to change the build stuff to adapt to this
concept? I have not looked closely.
Peace,
Dan
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
