1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On April 22, 2002 10:20 am, Alexander Gretencord wrote: |
5 |
> On Monday 22 April 2002 15:52, Todd Wright wrote: |
6 |
> > Either way, this is how it should be. We dont need all this extra (xml) |
7 |
> > pre processing. |
8 |
> |
9 |
> ACK |
10 |
> |
11 |
> > We just need a single config file (rc.conf) or a ../conf.d/ |
12 |
> > directory containing per package config variablle - but not both. |
13 |
> |
14 |
> Well I don't like the idea of a single file. It's easier to have a |
15 |
> directory with individual files so you can simply drop your file in there |
16 |
> if you need it. Just like the env.d. |
17 |
> |
18 |
> That two different paradigma are just confusing is (one point for) why I |
19 |
> don't like SuSE. They got a sysv init system but it just doesn't matter |
20 |
> what you do to the symlinks, you gotta edit rc.config too. |
21 |
> |
22 |
> Alex |
23 |
|
24 |
Note that xml could still allow you to have multiple file or a single one. |
25 |
Xml is made such that part of a file can be parse with different rules than |
26 |
other. There's also XLink that allow you to link xml content inside another |
27 |
file this allow someone to create many xml file and a master xml file telling |
28 |
where to look for the content. |
29 |
|
30 |
This allow a choice about a single or multiple files. |
31 |
|
32 |
The issue I think you want to refer to is duplication. Having a single or |
33 |
multiple xml cfg files + backward compatible cfg file could be a cost that |
34 |
will annoy users. For that I have yet to think about something interesting |
35 |
but I'll try, maybe the solution would just be to generate the backward |
36 |
comptaible files in hidden mode or in a hidden folder. That would make only |
37 |
advance users see them and play with them. |
38 |
|
39 |
- -- |
40 |
|
41 |
Yannick Koehler |
42 |
|
43 |
-----BEGIN PGP SIGNATURE----- |
44 |
Version: GnuPG v1.0.6 (GNU/Linux) |
45 |
Comment: For info see http://www.gnupg.org |
46 |
|
47 |
iD8DBQE8xB7NfuKOJNEyL1URAiXxAJ4535HrrCAop0GcrR2oTDRVkQCgKQCeK1kp |
48 |
hSDpp2NahEpHR5dPERtjfmk= |
49 |
=hHF0 |
50 |
-----END PGP SIGNATURE----- |