Bug#459244: asterisk: split-up proposal

Matthew King matthew.king at monnsta.net
Fri Jan 25 01:31:26 UTC 2008


Faidon Liambotis <paravoid at debian.org> writes:

> tag 459244 + wontfix
> thanks
>
> Matthew King wrote:
>> To the best of my knowledge the (mods|site)-(available|enabled) system
>> that Apache uses is something in Debian that has diverged from
>> upstream. At least insofar as their configuration doesn't use it by
>> default. The ability via the include directive is, of course, part of
>> upstream.
> What's the point?

To easily, and introducing no/very few errors, enable and disable
[un]wanted modules.

> Modules are enabled/disabled in modules.conf.
> Each module has a separate configuration file.
>
> How easier can it get?
>
> Apache is quite different FWIW.

In this case, Apache is the same. There used to be a list of modules to
load in the main configuration file [or in modules.conf depending on how
far back you look], this list is now split up into one module per .load
file[1]. Where necessary there is a corresponding .conf which *is*
different to Asterisk's approach but this difference is negligible[2].

'a2enmod something && apache2ctl graceful' is far easier than:

edit /etc/apache2/modules.conf
Find the module you wish to use and uncomment the necessary line.
  If it's not present, add it ensuring you get the syntax and fs path correct.
apache2 -t # Ensure the configuration is not broken
apache2ctl graceful

Note that not only is the latter, which is identical to the current
method employed by Asterisk, 2 [and a half] extra steps, but one is a
manual process with which it is possible to make a mistake.

Matthew

[1] I can't remember how dependant modules are dealt with. Either
there's some extra magic in the a2(en|dis)mod scripts or each .load file
lists all dependant modules and any resultant duplicates are ignored.

[2] That is to say, the .conf equivalent can be in /etc/asterisk while
the .loads are in /etc/asterisk/modules-(available|enabled). If the
module is not loaded the respective configuration file will simply be
ignored. In Apache the many small files are effectively concatenated
when the configuration is loaded.

-- 
I must take issue with the term "a mere child", for it has been my
invariable experience that the company of a mere child is infinitely
preferable to that of a mere adult.
                                           --  Fran Lebowitz





More information about the Pkg-voip-maintainers mailing list