Alright, after reviewing everything, I think that tying appinstall into <a href="http://test.winehq.org" target="_blank">test.winehq.org</a> along with adding more (if not most) of the wpkg scripts to appinstall would be most beneficial in terms of conformance and regression testing. Converting the wpkg scripts to appinstall doesn't seem like that difficult of a task, mostly just time consuming. That is why I thinking working on tying it into <a href="http://test.winehq.org">test.winehq.org</a> is more worthy. I still think tying appinstall and patchwatcher together would be beneficial and allow people submitting patches to see where regressions pop up in software, and to see what new software works with each submitted patch. Perhaps a project of implementing all of this and adding wpkg scripts would be accepted?<br>
<br>A little bit of background on myself, I am currently attending the University of Florida, seeking my undergraduate in mathematics. I've been an active linux user for several years. I've used wine for about as long. I have experience with writing the CUDA wrapper for wine, which is used mostly for folding at home. (Small fah plug, Folding at home is run by stanford to fold proteins and see how and why they fold or miss fold.� For more info see <a href="http://folding.stanford.edu/">http://folding.stanford.edu/</a> or <a href="http://www.overclockers.com/forums/forumdisplay.php?f=21">http://www.overclockers.com/forums/forumdisplay.php?f=21</a>).<br>
<br><br>Thanks,<br><br>Seth Shelnutt<br>