<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#666666">
<div class="moz-cite-prefix">Op 29-08-12 12:57, Benny Amorsen
schreef:<br>
</div>
<blockquote cite="mid:m3d32a9d9r.fsf@ursa.amorsen.dk" type="cite">
<pre wrap="">Michel Verbraak <a class="moz-txt-link-rfc2396E" href="mailto:michel@verbraak.org"><michel@verbraak.org></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">With this setup when a modules is ever renamed a new section is added.
People can customize to their own specifics.
An interface needs to be created which every module can call to locate
it's config files. Each module specifies it's own lineids to use but the
main/initial config file lineid is always "mainconfig".
</pre>
</blockquote>
<pre wrap="">
What is the use case though? Are there actual users who love to rename
their config files? Can't they make do with putting #include
real-config.conf as the only line of the traditional file?
Figuring out the Asterisk configuration is already a fairly daunting
task. Allowing the system to hide the configuration files makes it
worse, not better.
/Benny
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a> --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a>
</pre>
</blockquote>
<font size="-1"><font face="DejaVu Sans">In my proposal it is easier
to see which configuration files are used by which module. Just
have a look into the modules.conf and it shows them all.<br>
If someone wants to rename config files it is up to them. On use
case could be a second instance of asterisk reusing some of the
config files of the first instance. <br>
<br>
Michel. <br>
</font></font>
</body>
</html>