[wpkg-users] xml Elements and attributes

[Charles Gargent]

2009/7/15 Charles Gargent <charlesgargent at gmail.com>:
> 2009/7/15 Rainer Meier <r.meier at wpkg.org>:
>> Hi Charles,
>>
>> Charles Gargent wrote:
>>> IMHO it makes more sense to have everything one way or t'other, I
>>> appreciate that converting everything to elements would break
>>> compatability, so would it be possible to convert the exitcode and
>>> reboot data to an attribute like so
>>>
>>> <remove cmd=' some command....' exitcode='any' reboot='delayed' />
>>>
>>> instead of
>>>
>>> <remove cmd=' some command....'><exit code='any' reboot='delayed' /></remove>
>>
>> This would break an essential function of WPKG. It would not be possible any
>> more to define multiple exit codes with different actions (define success,
>> reboot, delayed reboot). Using attributes here would allow only one exit code
>> definition. So we need multiple exit code sub-elements to the commands.
>>
>> Moreover even this would break compatibility and needs coordination with 3rd
>> party tool developers (eg. wpkgExpress).
>>
>> So I don't think it's a good idea. I can't think of any benefit but the drawback
>> of this change is clearly visible.
>>
>> br,
>> Rainer
>>
>
> Ah Good point, I had forgotten about the multiple exit codes.
>

Is it possible to change the install, upgrade & remove elements to an
"action" element and then have the type of action listed as an
attribute such as

<action type="install" cmd="....

or will this be too difficult