[asterisk-users] Re: Zaptel install - Fedora Core 5

[Tzafrir Cohen]

On Tue, Aug 22, 2006 at 11:16:38AM -0500, Rich Adamson wrote:
> Tzafrir Cohen wrote:
> >On Tue, Aug 22, 2006 at 08:42:36AM -0500, Rich Adamson wrote:
> >>Tomislav Parčina wrote:
> >>>In article <007a01c6c55f$ee353ff0$0e66970a at ds.mot.com>, 
> >>>aryanto at chello.at says...
> >>>>I did "yum update" last week and here is my current kernel:
> >>>>
> >>>>I had no problem at all with zaptel. I am only using TDM400P though, in
> >>>>case that matters.
> >>>
> >>>Hi Anto!
> >>>
> >>>The thing is that I can't rely on yum update for asterisk installation. 
> >>>I would like something that will work like this: I install FC5 from 
> >>>CD/DVD, install RPM's that I need from my ftp server or from CD, install 
> >>>zaptel, libpri, asterisk...
> >>>
> >>>So, I need to download rpm's that will allow me to install 
> >>>zaptel/libpri/asterisk without using yum update (I need to make all 
> >>>installations the same).
> >>Why bother with the rpm's?
> >
> >Because you have some other programs on your system other than Asterisk.
> >
> >And because you want a reproducable build.
> 
> Guess that depends a lot on personal objectives, styles, and whether 
> asterisk code has been modified locally. Once the reproducable build is 
> operational and one has to maintain the code, reproducable builds sort 
> of go out the window (eg, customer/system A has a problem, but not 
> customer B through Z).

The flip side to this is that only A will get the fix, and not B to Z.
This is why also we try to make sure things will be customizable at 
run-time.
However, if you need to provide the same build to both system A and
system B, there's double work.

> 
> Using the Branch SVN checkout approach always provides the most up to 
> date code as opposed to replicating buggy stuff via rpms.

What's the problem of building an rpm vs. latest 1.2 / trunk? The only
issue is the existing patches. I posted a few monthes ago how to use an
'external' to get the debian/ directory from the pkg-voip repo nd build
a package directly from svn using svn-buildpackage. Pick your
branch/tag.

You may have a set of local changes you wish to maintain. The way of
rpm/deb is to maintain them as a set of patches.

One possible alternaitve is to try to use an Svk repository with the
Digium repo as an aside "upstream". It would still be a bit tricky.

-- 
Tzafrir Cohen         sip:tzafrir at local.xorcom.com
icq#16849755          iax:tzafrir at local.xorcom.com
+972-50-7952406          jabber:tzafrir at jabber.org
tzafrir.cohen at xorcom.com     http://www.xorcom.com