asterisk users - Mar 2005 - how to keep Asterisk up to date on many servers

Hi Everyone.

Asterisk is one of those applications that need to be built from cvs on a
regular basis to keep up with the changes.  I have always used package
management tools like apt.

How does everyone manage their Asterisk servers?

Geoff

Geoff Nordli wrote:
> Hi Everyone.
> 
> Asterisk is one of those applications that need to be built from cvs on a
> regular basis to keep up with the changes.  I have always used package
> management tools like apt.
> 
> How does everyone manage their Asterisk servers?
> 
> Geoff
Geoff,

	Probably the easiest way is to tweak the DESTDIR= variable in the * 
Makefile and install it into an alternate root ("/opt/asterisk", or 
something).  Don't forget to use the upgrade target (make upgrade), 
otherwise it will put configs there, and you probably don't want that... 
  Then you can tar.gz that directory up (make sure not to preserve the 
/opt/asterisk), and then un-tar that on your machines.  Or use rsync, or 
get fancy with one of those uuencoded shell scripts that people use for 
software distribution on Linux:

option 1)

cd /usr/src/asterisk
vi Makefile (edit DESTDIR)
mkdir /opt/asterisk
make upgrade
cd /opt/asterisk
tar -cvjf ../asterisk.tar.bz2 *
(distribute your tar.bz2 to a remote machine)

REMOTE MACHINE: cd / ; tar -xvjpf /path/to/tar

	This can be tricky because you will have to make sure that your build 
host and target host(s) are more or less the same: libpri yes/no, zaptel 
yes/no, processor family, etc.  I would just do this for libpri, zaptel, 
and asterisk (put them all in /opt/asterisk, your alternate root 
directory on the build system), and then tar it up.  I hope that this 
makes some sense, it is getting pretty late here...

--
Kristian Kielhofner

On Mon, Mar 21, 2005 at 09:36:53PM -0800, Geoff Nordli
wrote:
> Hi Everyone.
> 
> Asterisk is one of those applications that need to be built from cvs on a
> regular basis to keep up with the changes.  I have always used package
> management tools like apt.
I am known to always stick with the package management tools. And (re)build
packages if I have to. Installation takes longer the firs time.
Maintinance is much easier in the long run.
> 
> How does everyone manage their Asterisk servers?
You can build your own packages and put them in your local repository
for your local installation. 

I'm not aware of anybody building packages of Asterisk's cvs HEAD . The
Debian packages are from the stable branch. I figure you could adapt
them and use cvs-buildpackage if you're on Debian to automate building
from HEAD.

-- 
Tzafrir Cohen         | New signature for new address and  |  VIM is
http://tzafrir.org.il | new homepage                       | a Mutt's  
tzafrir@cohens.org.il |                                    |  best
ICQ# 16849755         | Space reserved for other protocols | friend

On Mon, 21 Mar 2005 21:36:53 -0800, Geoff Nordli <geoffn@gnaa.net>
wrote:
> Hi Everyone.
> 
> Asterisk is one of those applications that need to be built from cvs on a
> regular basis to keep up with the changes.  I have always used package
> management tools like apt.
> 
> How does everyone manage their Asterisk servers?
> 
> Geoff


I use Asterisk stable, which is updated frequently enough for my liking.

I use Debian Woody on my servers.

I have Asterisk already running, and my service is interrupted only briefly.

Here's what I do:

Download the packages to /usr/src/.

tar zxvf zaptel-1.0.7.tar.gz
cd zaptel-1.0.7/
make clean
checkinstall -D --pkgname=zaptel --pkggroup=Asterisk
--maintainer=myemail@ddress --dpkgflags=--force-overwrite --nodoc
--default -bk --pkgrelease=`uname -r` --pkgversion=1.0.7
mv zaptel_1.0.7-`uname -r`_i386.deb ../debs/
cd ..
tar zxvf libpri-1.0.7.tar.gz
cd libpri-1.0.7/
make clean
checkinstall -D --pkgname=libpri --pkggroup=Asterisk
--maintainer=myemail@ddress --dpkgflags=--force-overwrite --nodoc
--default -bk --pkgversion=1.0.7 --pkgrelease=1
mv libpri_1.0.7-1_i386.deb ../debs/
cd ..
tar zxvf asterisk-1.0.7.tar.gz
cd asterisk-1.0.7/
make clean
checkinstall -D --pkgname=asterisk --pkggroup=Asterisk
--maintainer=myemail@ddress --dpkgflags=--force-overwrite --nodoc
--default -bk --pkgversion=1.0.7 --pkgrelease=1
mv asterisk_1.0.7-1_i386.deb ../debs/
cd ..
tar zxvf asterisk-sounds-1.0.7.tar.gz
cd asterisk-sounds-1.0.7/
checkinstall -D --pkgname=asterisk-sounds --pkggroup=Asterisk
--maintainer=myemail@ddress --dpkgflags=--force-overwrite --nodoc
--default -bk --pkgversion=1.0.7 --pkgrelease=1
mv asterisk-sounds_1.0.7-1_i386.deb ../debs/

This builds and installs all of the packages I use and then puts the
resulting .deb packages into /usr/src/debs. I can then copy the .debs
to other servers and just install them with dpkg -i --force-overwrite.

Works like a charm for me.
--
Dana