http://bugs.winehq.org/show_bug.cgi?id=9628
--- Comment #13 from Darragh Bailey felix@compsoc.nuigalway.ie 2008-04-14 15:01:16 --- (In reply to comment #12)
If you test CreateProcess, GetCommandLine, and CommandLineToArgv, you don't need to test msiexec. We know that it's failing; it's how we can correctly fix it that matters. We need to know the exact behaviors of these three APIs in the circumstances in question, and once we do, we can fix msiexec.
Not following the logic.
I've confirmed that CreateProcess, GetCommandLine, and CommandLineToArgv do not behave on windows in such a manner that would allow msiexec to use them directly and produce the observed results on windows, i.e. that the xlviewer and RPG maker installers both function.
So AFAICT, it cannot use a win32 api call to get argv correctly for all cases that it can handle on windows. Does this not mean that the custom handling of argv in this case should also result in a test case added to make sure it doesn't break in the futre? Or is there some other api call that can be used that will satisfy the required behaviour?