When a new module is created, the author will include a configuration file with default values. When the module is installed, this file will be copied to the config directory and read into the active store. Future changes will be written to the file in the config directory. This whole process needs to be implemented. I think that one of the big questions is how these files will be discovered. My preference would be that we look for a specially named directory like 'config' and just consider anything in there with a defaut.xml file name to be config that gets moved to the active area. Later we may want to do something where the config files are more specifically declared (in the info file maybe) but I think we can hold that for later.
Comment | File | Size | Author |
---|---|---|---|
#5 | 1288102-basename.patch | 1.75 KB | Xen |
#1 | 0001-Fixed-defaults-loading.patch | 1.45 KB | Xen |
Comments
Comment #1
Xen CreditAttribution: Xen commentedLatest head has code that almost works. This really works.
Comment #2
gddAh I was working on fixing this, but your version is a lot simpler. I'm going to commit this right now.
Comment #3
naxoc CreditAttribution: naxoc commentedYes it works. The installer does not die now anymore.
Comment #4
gddComment #5
Xen CreditAttribution: Xen commentedPassing by the code, I thought this is a bit more elegant.
Comment #6
Xen CreditAttribution: Xen commentedOh, and
should be removed, it's not used.
Comment #7
sun