[asterisk-users] Installing Asterisk to it's own directory

[Stephen Brown]

Thanks... I actually did a ./configure --prefix=/root/asterisk18 and 
ended up with this:

root at debian-squeeze:~/asterisk18# pwd
/root/asterisk18

root at debian-squeeze:~/asterisk18# ls -al
total 32
drwxr-xr-x 8 root root 4096 Nov 19 18:09 .
drwx------ 5 root root 4096 Nov 19 18:37 ..
drwxr-xr-x 3 root root 4096 Nov 19 18:09 etc
drwxr-xr-x 3 root root 4096 Nov 19 18:09 include
drwxr-xr-x 3 root root 4096 Nov 19 18:09 lib
drwxr-xr-x 2 root root 4096 Nov 19 18:09 sbin
drwxr-xr-x 3 root root 4096 Nov 19 18:09 share
drwxr-xr-x 6 root root 4096 Nov 19 18:09 var

Have I essentially accomplished the same thing by doing it this way? 
This is in a virtual machine alongside an Asterisk 1.6 install (for 
testing), I'm still a little gunshy to touch my production box as of 
yet..... but the 1.8 install did work, I was able to make a call to the 
demo context :)

Thanks,
Stephen

On 11/19/10 10:13 PM, Jose P. Espinal wrote:
> Hi Stephen,
>
> That's what people do when building precompiled packages for certain
> distros (along with a few more things).
>
> I use to do the following when building packages (with a few more options):
>
> ./configure --prefix=/usr --sysconfdir=/etc
> make
> make install DESTDIR=/my/destination/directory
>
> That would create the complete installation structure under
> '/my/destination/directory'
>
>
> Regards,
>
>
>
> Stephen Brown wrote:
>> I'd like to start playing with 1.8, however I don't want to potentially
>> damage anything on my existing 1.6.2 install on my production server.
>>
>> I'd like to test 1.8 against my existing configs leaving my 1.6.2
>> install untouched. Looking at the output of ./configure --help suggests
>> that it's possible to install Asterisk into another prefix of my
>> choosing, but as this is unfamiliar territory to me I'm not exactly sure
>> how to accomplish this?
>>
>> Ideally, I'd like to just dump the newly compiled 1.8 and all it's
>> dependencies into a standalone directory (say /testing/asterisk or
>> something) and update my init script to point to the new binaries. I
>> also run a Sangoma USB FXO card and DAHDI for a POTS line that I would
>> like to test as well, should it work with the pre-compiled binaries that
>> are already there? (DAHDI, etc)
>>
>> I've never tried this before, and before I potentially break something
>> I'd like to know if it's possible and how to implement it?
>>
>> Thanks,
>> Stephen
>>
>>
>>