Hi Thiago,<br><br><div><span class="gmail_quote">On 6/13/07, <b class="gmail_sendername">Thiago Macieira</b> <<a href="mailto:thiago@kde.org">thiago@kde.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Rudi Cilibrasi, Ph.D. wrote:<br>>Would it make sense to just have some sort of "include file" facility<br>> for /usr/share/dbus/services and let the OS config tools / sysadmins<br>> handle the organization? Best regards,
<br><br>Sorry, I did not understand you. What do you mean?<br><br>The paths for those can be defined in the system.conf and session.conf<br>files. However, changing them might not be wise: program installations<br>will create files in those dirs and expect them to work.
</blockquote><div><br><br>I meant that we can avoid having to have more than one application change the<br>same file by using file-inclusion the same way other servers or software systems<br>that must share config information do. Here is an example:
<br><br>grep /etc/default/rcS /etc/init.d/* <br></div><br>/etc/init.d/hwclock.sh: . /etc/default/rcS<br>/etc/init.d/x11-common:. /etc/default/rcS<br>... etc.<br><br>The thing to notice here is that in the language being used (sh), there is a "modular"
<br>include facility using the "source" (".") command that lets more than one "init script"<br>load the same adjustable config file in a shared way that lets the sysadmin and<br>developers work out their own organization and plan to prevent the system tools from
<br>messing up config files. Notice that the files in /etc/init.d can often be customized by<br>the user on a per-application basis, but still they both use a common file also. This is<br>a nice flexible design I think. So this is only possible with languages that support some sort of inclusion of a file within a file like "#include" in C, or "require" in Ruby.
<br>I was suggesting that we make sure the services file language supports some <br>sort of arbitrary inclusion in this way so that is makes it easier<br>to manage shared or strangely changing config files. So it was supposed to address your
<br>concern of not having more than one application have to potentially adjust the same file and<br>therefore interfere with each other. Best regards,<br><br>Rudi<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
--<br> Thiago Macieira - thiago (AT) <a href="http://macieira.info">macieira.info</a> - thiago (AT) <a href="http://kde.org">kde.org</a><br> PGP/GPG: 0x6EF45358; fingerprint:<br> E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
<br><br>_______________________________________________<br>dbus mailing list<br><a href="mailto:dbus@lists.freedesktop.org">dbus@lists.freedesktop.org</a><br><a href="http://lists.freedesktop.org/mailman/listinfo/dbus">http://lists.freedesktop.org/mailman/listinfo/dbus
</a><br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Democracy is two wolves and a sheep deciding what to eat for lunch.<br>Liberty is a well-armed sheep contesting the vote.