Uwe Gansert wrote, On 01/22/2010 01:31 AM:
on Thursday 21 January 2010 Stephen Dowdy wrote: ...
From this example, all i can infer is that a <match> element value is used as a non-anchored match string. ("match anywhere") ... But what is the full-extent of what i can use here?
it's a simple bash "=~" if [[ "uwe gansert" =~ u.e\ g[abc]ns ]]; then echo jo; fi
Ah, okay, great, that helps a lot. Indeed [..] character set matching works for "<product>\n<match>PowerEdge [12]850</match>" in my rules.xml file for this particular set of machines. I hope i'm not being pushy, but if you could update the AutoYast docs to reflect just what you said above, it'd be very helpful. (and possibly use a slightly more complex example than the "<match>ntel</match>" one you have.) ------------ 6.1.3. Match Types for rules .. regex can be used to match substrings like "ntel" will match "Intel","intel" and "intelligent". ------------
but while looking at the code a few minutes ago, I noticed a bug in it :( Currently only substring matching seems to work properly which is what I used for testing the code when I implemented it :-/ I have to test that but by looking at the code, it looks like a bug
Well, My Dell 8th Gen Profile got pulled in by this rule just now:
<!-- Different Network Configuration for PE1850/PE2850s -->
<rule>
<product>
<match>PowerEdge [12]850</match>