[wpkg-users] [Bug 209] Replace variables in package revisions by their value in local wpkg.xml file

bugzilla-daemon at bugzilla.wpkg.org bugzilla-daemon at bugzilla.wpkg.org
Sat Jul 9 16:43:09 CEST 2011


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

--- Comment #13 from Rainer Meier <r.meier at wpkg.org>  ---
Just committed a larger change which potentially fixes the problem:

FIX: Extended host attribute matching uses "hostname" now for host name
     matching to prevent collision with name attributes in <variable />
     nodes. Moreover this allows now to use classical "name=" attribute
     in <host /> nodes as wel as the "hostname" extended match attribute.
     In addition the "name=" attribute in <hosts /> have been declared as
     optional now. This allows to use either legacy "name" matching which
     does direct literal-match, IP-address match and regexp matching as well
     as it allows to use extended host match attributes instead.

     E.g. the following constructs are valid...
     Classial host matching:
     <host name="hostname" profile-id="p" />

     IP-matching using classical name attribute:
     <host name="192.168.1.1-255" profile-id="p" />

     Alternative matching using extended host attributes omitting name
     attribute:
     <host ipaddresses="192\.168\.1\..*" profile-id="p" />

     Combining classical matching with extended host matching:
     <host name="hostname" os="windows 7" profile-id="p" />
     Fixes additional bugs found in implementation for bug 209.
     Thanks to Stefan Pendl.


In fact this allows to declare the "name" attribute in hosts as "legacy" and
optionally match hosts entirely by extended host matching attributes. The
special name-attribute matching is now used only when matching hosts in
hosts.xml.

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.



More information about the wpkg-users mailing list