http://bugzilla.wpkg.org/show_bug.cgi?id=249

Rainer Meier <r.me...@wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r.me...@wpkg.org

--- Comment #1 from Rainer Meier <r.me...@wpkg.org>  ---
1) The condition and check nodes are moved to a generic namespace. So you would
have to qualify them:

        <include package-id="JRE6">
            <wpkg:condition>
                <wpkg:check type="logical" condition="or">
                    <wpkg:check type="host" condition="hostname"
value="SATELLITE"/>
                    <wpkg:check type="host" condition="os"
value="5\.0\.\d{4}"/>
                </wpkg:check>
            </wpkg:condition>
        </include>

While importing the namespace in the header like this:

<packages:packages xmlns:packages="http://www.wpkg.org/packages";
    xmlns:wpkg="http://www.wpkg.org/wpkg";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
    xsi:schemaLocation="http://www.wpkg.org/packages xsd/packages.xsd">

Well, this imposes a couple of other issues like wpkg.js not fetching the
conditions.

To solve this I've decided to change to unqualified element form default to
hide the namespaces included.

So now you can use unqualified elements as follows:

<packages:packages xmlns:packages="http://www.wpkg.org/packages";
    xmlns:wpkg="http://www.wpkg.org/wpkg";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
    xsi:schemaLocation="http://www.wpkg.org/packages xsd/packages.xsd">
...
        <include package-id="JRE6">
            <condition>
                <check type="logical" condition="or">
                    <check type="host" condition="hostname" value="SATELLITE"/>
                    <check type="host" condition="os" value="5\.0\.\d{4}"/>
                </check>
            </condition>
        </include>
...

</packages:packages>


2. "include" attribute of <command /> just accepts
install/upgrade/downgrade/remove values.

This has been changed. Now allows any string.



No, you do not pester me to death. We have added many features recently and a
pile of bugs was expected. That's why we are testing.

Changes 2011-10-28, v1.2.1-RC40 by Rainer Meier <r.meier (at) wpkg.org>
FIX: Conditional expressions are defined in generic wpkg namespace at
     http://www.wpkg.org/wpkg. Element form default has been set to unqualified
     in order to hide (localize) namespaces. Thus eliminating the requirement
     to specify condition and check nodes with namespace qualifier.
     Fixes bug 249. Thanks to Stefan Pendl for reporting.
FIX: Within the <command /> node the "include" attribute shall allow any string
     to be used. Not just install/upgrade/downgrade/remove.
     Fixed in XSD.
     Fixes bug 249. Thanks to Stefan Pendl for reporting.

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

Reply via email to