[ATrpms-users] Asterisk dependencies

[Axel Thimm]

On Wed, Jul 05, 2006 at 03:22:37PM -0600, Philip Prindeville wrote:
> Ok, I'm unclear.  The version on ATrpms:  is this just a build for FC5 of
> the stock version (since it's not carried by Redhat in the FC5 distro), or
> have their been any changes made to it?

Just like all other packages asterisk is only patched up when there
are bugs surfacing in the distro it is to be run on or to accommodate
it to the distro (some upstream projects don't follow FHS, or
sometimes you need Red Hat specialities like /etc/sysconfig stuff)

> >>>>Could the timing module ztdummy (since it doesn't actually
> >>>>correspond to real hardware, if I've understood correctly) be
> >>>>made part of a stand-alone asterisk-kmdl rpm instead?
> >>>>    
> >>>Technically yes, but what would the gain be? A smaller kmdl
> >>>package?  Zaptel kmdls are about 250-350k, not really big (if
> >>>compared for instance to the kernel rpm).
> >>>      
> >>Well, I'm thinking that most of the zaptel package should be
> >>support for various physical cards.  If you're running pure VoIP
> >>with SIP peering with other call-managers, then you don't need to
> >>support any sort of trunking (FXS, FXO, PRI, T1/CCS, etc).
> >>    
> >OK so far, but where is the drawback in having all of them? The
> >loss of 200k?
> 
> The issue is that all Asterisk installations require ztdummy from
> what I can tell, so it should be part of the core fileset.
> 
> Not all installations (especially those with SIP phones) don't require any
> hardware support, since the phones themselves are network attached devices.
> 
> In a SIP-handset only config, you should be able to get by without the
> zaptel kernel modules.

It seems we're arguing in circles. :)

My question is: Does it really hurt you that there are 200k worth of
kernel modules for hardware you don't use installed? You probably only
use 1/20th of the kernel rpm, so you have a "slack space" of several
MB there.

> >You could argue about the whole kernel rpm that way, and people with
> >that hardware would prefer not to have drivers for all the other
> >hardware etc.
> 
> Well, I'm willing to divide the universe into installs with hardware
> (key-sets, analogue handsets, etc) versus installs without hardware
> (where all the phones are network devices and don't require any
> device drivers local to the Asterisk PBX application server).

So you would split the kernel into kernel-filesystems,
kernel-hardware-drivers, kernel-software-drivers, too?

Red Hat/Fedora is an "all-inclusive distro", e.g. there isn't really a
micro-granularity of packages like sometimes found on Debian (which
BTW doesn't split zaptel up). The only reason for micro-granularity is
for embedded systems, where any resource counts and when some parts of
the package pull in tons of other packages - in the latter case
splitting the part that pull in all other parts allows the user to
have a minimal install.

But for something the size of 1/7th of a floppy it just isn't worth
it. :)
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20060706/948b2055/attachment.bin