| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
|
| 5 |
So far what I learned is that the whole system should be optionnal. It must |
| 6 |
retain support for existing configuration files for several reasons such as |
| 7 |
working with current applications. It must not gives a feeling of |
| 8 |
duplication but still provide a comprehensive way for software to deal with |
| 9 |
the various configuration. |
| 10 |
|
| 11 |
The idea is evolving a little more. What if the system was not going to |
| 12 |
create files, but was going to apply transformation rules from a given folder |
| 13 |
when reading the file and then parsing it internally into xml to then use |
| 14 |
inside some kind of application like merge or configurator. |
| 15 |
|
| 16 |
So you'll have /etc which remains intact, a software that is optionnaly |
| 17 |
installed with a bunch of transformation text file such as xslt which would |
| 18 |
provide instruction to the software on how to parse the original file and |
| 19 |
transform it into an xml one. Then using xml tools merge software could be |
| 20 |
written and xml editor used. The xml then become a software interface and |
| 21 |
never interfere with existing etc folder. |
| 22 |
|
| 23 |
What do you think on that one? |
| 24 |
|
| 25 |
- -- |
| 26 |
|
| 27 |
Yannick Koehler |
| 28 |
|
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.0.6 (GNU/Linux) |
| 31 |
Comment: For info see http://www.gnupg.org |
| 32 |
|
| 33 |
iD8DBQE8xEaZfuKOJNEyL1URApUIAKCkTrBXoDJC+m2zVMfGfnm+wWOxyACfbrq+ |
| 34 |
aryxixkijdj5YUixaeTpLq0= |
| 35 |
=jJaO |
| 36 |
-----END PGP SIGNATURE----- |
Archives