Tomasz Chmielewski schrieb:
> Marco Gaiarin schrieb:
>> Mandi! bugzilla-daemon@bugz...
>>   In chel di` si favelave...
>>
>>> About config.xml. There is a bug within 0.9.12-test3 that config.xml is nonly
>>> read if the script is executed within the same directory (config.xml exists
>>> within working directory). In case of remote-execution (e.g.
>>> \\server\share\wpkg.js) the script file cannot be found. Some people might not
>>> have recognized this since test3 was designed to work with default values even
>>> if config.xml does not exist (exactly like my modification). This has been
>>> fixed now.
>> Sorry, i think i'm missing something.
>>
>> But settings.xml values are 'imported' using, eg:
>>
>> wpkginst.exe --SETTINGSFILE=%WPKGROOT%\settings.xml
>>
>> or are read by wpkg service every time?
>
> settings.xml and config.xml are two different files distributed in two
> different packages: settings.xml is to be used with WPKG Client, and
> config.xml is to be used with wpkg.js.

I added some brief description here:

http://wpkg.org/Config.xml
http://wpkg.org/Settings.xml

If something is not very clear, feel free to correct it.


--
Tomasz Chmielewski
http://wpkg.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
wpkg-users mailing list
wpkg-users@list...
https://lists.sourceforge.net/lists/listinfo/wpkg-users