[[User:StefanP|StefanP]] 19:31, 27 July 2011 (CEST)
: I thought they could be useful if you are going to prepare your packages for a specific OS. Of cause everybody can check them out from the logs, but if you are in the process of setting up packages for new OSs the list might come handy. I personally really would like to know what OS strings there are "in the wild".
I thought : When building regular expressions it is always nice to know what strings they could be useful if might match. Sure, you are going to prepare can parse your packages for a specific OS. Of cause everybody can check them out from the logson your own, but isn't it nicer if you are in the process of setting up packages for new OSs the there is some community driven list might come handy. I personally really would like to know what OS strings there are "in the wild".already available?
When building regular expressions it is always nice to know what strings they might match. Sure, : If you can parse your logs on your own, but isndon't it nicer if there is some community driven like the idea, feel free to remove the list already available?I have started.
If you don:: I do not think about removing it, but about its usefulness. :: Wouldn't like a generic list be as good?:: Who really needs the ideadifferent editions of Win7 (Ultimate, feel free to remove the list Professional, Home, Starter), if there is no significant difference? :: I have startedenvision a list of pattern matches like below. :: Windows XP SP2 ................. os="sp2.+5\.1\.[0-9][0-9][0-9][0-9]":: Windows 7/Server 2008 R2 ... os="6\.1\.[0-9][0-9][0-9][0-9]":: Windows Server 2008 R2 ...... os="server.+6\.1\.[0-9][0-9][0-9][0-9]" :: This would be something a user can use directly, without the need to invent match pattern on their own. :: What do you think?:: [[User:StefanP|StefanP]] 00:04, 1 August 2011 (CEST)