На Sat, 05 Jan 2008 03:03:05 +0200
Faidon Liambotis <[EMAIL PROTECTED]> записано:
> You can always disable autoload and load only the modules that you
> want to. You can leave them unconfigured or even remove the
> configuration files. With the current infrastructure you can even
> provide a configuration file package to not include these files *at
> all*.
Ok. May be there should be a configuration dialog with all possible
modules, allowing me to check what modules are "active" ? While
"passive" are kept in some other place, with their config respectivly.
I've tried to remove unused config files, but it seems to me it is not
the best solution so far - not every module refuses to load without
config, some of them constantly logging an error, and there is no good
to see many complaints at asterisk booting.
> That is an actual reason.
> I've thought about it myself, splitting some modules to different
> packages to minimize the dependency chain.
>
> I'm leaving this open, because it's a valid request -for that last
> reason- that needs a little bit more though.
>
> Don't expect us to split asterisk to 48 packages though, there's no
> way this is going to happen ever.
Could we agree that keeping every module and it config in one place,
and enablig it to autoload by default is just not the "right thing" ?
For example, there are orphaned config files - just because there are
too many of them to get it in one sight.
It seems to me a better way is, if it is not possible to split-up
everything to it own package with current infrastructure, to have:
1. modules with extra dependencies splitted to a separate packages,
just like you suggested
2. a configure dialog script allowing to select what modules are "on"
and "off", just like apache do.
even more, asterisk menuselect allows user to select what application to
have installed, but with current packaging scheme this functionality is
lost.
--
With best regards,
Roman Galeyev.
