From: Elias N. <na...@od...> - 2006-07-21 15:48:10
|
On Friday 21 July 2006 16:37, Chris Sutcliffe wrote: > > It seems that other GUIDs was extracted with a C program and a script so > > I re-implemented that solution and extracted all GUID_DEVCLASS_* symbols > > and values from Uuid.lib. I've submitted a patch with the extractor and > > the actual changes to w32api: > > There was some concern as to how the original libuuid.a was > implemented in terms of GUID definitions (given the comment about the > C program / script usage against uuid.lib that I expect you have also > read). As a result the original libuuid definitions have been > replaced by extracting the IIDs, UUIDs and GUIDs from the Windows > Registry. > > As such, the patch you created by extracting the definitions from > uuid.lib directly cannot be accepted. If these values can be found > from a public source (i.e. the Windows registry) than they would be > accepted. > > Chris I can understand the thin legal line you're trying not to cross, so I'll see if I can come up with alternative ways to fetch the UUIDs (I did look in the registry like the other *-uuid.c files commented but came up emptyhanded). In the meantime would you consider taking the logical next step of legal uncertainty and delete uuid.c? That way, other potential contributers like me won't be fooled to think that the extraction method is acceptable. I don't think uuid.c is actually referenced anywhere. - elias |