Alright after creating a few test scripts and playing around with things I think I have finally settled on exactly what my proposal is. It is in three parts,<br><br>1) Convert wpkg (or appDeploy) scripts into ahk scripts. I believe that I can convert a hundred or so without to much work.<br>

<br>2) I&#39;d like to implement a more aggressive error reporting. I want to have appinstall rerun failed test using WINEDEBUG=+all (or possibly have it guess what channel is needed to be watched). Saving the output of this will allow one to more easily debug the program. You won&#39;t have to go back and rerun the program yourself in wine, you will already be given the output so you can see what failed, where.<br>

<br>3) I&#39;d also like to implement a feature to have the output more in the format of <a href="http://test.winehq.org">test.winehq.org</a>. I am thinking that it would be easier to have it done split into two scripts, one on client-side, one server-side. Have the client format all the information into an xml file, and then server-side convert that xml into something along the lines of what <a href="http://test.winehq.org">test.winehq.org</a> looks like.<br>

<br>I can go more in depth with each step I&#39;d like to take, but I am not sure how specific I should be with my proposal? I was looking at last year&#39;s proposals and they didn&#39;t seem overly in depth on the steps they planned to take.<br>

<br><br>The five sample scripts and the edited appinstall.sh can be found here, <a href="http://shelnutt2.host56.com/appinstall/">http://shelnutt2.host56.com/appinstall/</a> . I&#39;ve found the easiest way to add the scripts is to copy them into the ~/.appinstallcache folder after it&#39;s created and before the tests are run.<br>

<br><br>Thanks,<br><br>-Seth Shelnutt<br>