> > So for now the algorithm to match the name attribute is > exactly identical to > previous WPKG versions: > 1. Try to match the strings 1:1 > 2. Try to match IP-addressees > Format: "<range>.<range>.<range>.<range>" > where <range> is either a digit between 0 and 255 or a > range in the format > "x-y". > e.g. "192.168.0.1-255" > 3. Transform attribute value into regexp by prepending "^" > and appending "$": > "test" becomes "^test$" > This mode is often used to match multiple hosts with a > naming scheme. > e.g. "lab-.*" becomes "^lab-.*$" > > Do not confuse (3) with the new extended host matches. If you > want to use the > hostname attribute instead of the name attribute you have to specify > hostname="^lab-.*$" directly. > > That's all. > > > > The new extended host matching seems to be more robust due > to separating the attributes. > > This is absolutely clear. The approach of "name" was to > detect the user > intention and match the values in a smart way. In fact I > think the algorithm to > match ip-addresses is pretty smart, but as I see with test 22 > it was also > misunderstood. The regular expression mode of the name > attribute does not apply > to IP-addresses. If you want to match IP-addresses with the > name attribute they > need to be specified in range-format with exactly 3 > separating dots in the > expression. > Thanks for clarifying this, so I have to change my hostname match of a package in a profile to make it bulletproof ;-) I like how things are coming into shape ;-D Have a pleasant one, Stefan |