Miloslav Trmac <mitr volny cz> wrote: > Can all configuration files be _usefully_ represented by a hierarchy? > The natural format (= format prefered for human editing) for some > applications uses m4 (sendmail, SELinux policy) or even arbitrary > PHP/perl code. Those ones you cited are the perfect examples of how badly designed these configurations are, because they allow mixing of configuration elements with pure business logic. Although this is powerful, the business logic should not be mixed with configuration elements. Just to cite an example, Unix filesystem (a.k.a. FHS) is designed with this separation in mind: logic, configuration, data, logs. We are getting too philosophic here... Avi -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
