Get some feedback on the following....<br><br>For the cache_dir creation....we make a function to do the tests to see if ~/.pony_build exists...<br><br>1) If it does just return true<br>2) If it doesn't make it and return true.<br>
3) Return false if it cant. Just to be complete i guess.<br><br>The code for this should be trivial.<br><br>Inside the *Clone classes, you just call it before you start running the checkout stuff, or maybe just have it run before any of the *Clone classes are called. Either way, .pony-build will always be created if it is not there...then inside the different classes you just do the tests for the repo_dir and do the initial co's when needed.<br>
<br>Those are my thoughts on the next step for "prettying" the implementation up.<br><br><br><div class="gmail_quote">On Sun, Jan 24, 2010 at 10:05 PM, C. Titus Brown <span dir="ltr"><<a href="mailto:ctb@msu.edu">ctb@msu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Sun, Jan 24, 2010 at 07:06:44PM -0400, Max Laite wrote:<br>
> Yes, I will move the .pony-build dir creation to its own function.<br>
><br>
> I took the lazy way out at the time, I just ran through a few build scripts,<br>
> deleting the main cache_dir and the repo dirs after each run to test the<br>
> different cases.....<br>
<br>
</div>Nothing wrong with lazy, as long as we go back and fix it :). Check<br>
out the term "technical debt"...<br>
<div class="im"><br>
> Yes, I need to work on standardizing my indents and comments. Have no fear,<br>
> I will get some consistency by the end of the semester!<br>
<br>
</div>Many editors will help you out the indent level -- I use emacs, which takes<br>
care of a lot of that myself.<br>
<div class="im"><br>
> I will look at your script, I need to do some catching up on testing stuff<br>
> the proper way (easy way?).<br>
<br>
</div>It's a mildly sticky problem; if it were trivial, I would have set up at least<br>
some client test scripts myself. What I've decided to start doing is what I've<br>
done with test-git: develop some simple scripts to run obvious tests, and then<br>
integrate them into an automated test suite later.<br>
<br>
cheers,<br>
<font color="#888888">--titus<br>
</font></blockquote></div><br>