<br>I typically build separately on my backend & frontend. I just do a snv update, and then compile everything.<br><br>But, now I'm adding a separate backend, and it's time to upgrade svn (why not?), so I thought I'd pose a question: How would you recommend doing the svn build? I can think of a couple of possibilities:
<br><br>1) Have separate build directories on each machine. Update one, make not of the rev. Then update all others with -r rev, make everywhere and deploy.<br>2) Use one shared build directory. Update once, and install everywhere. Not sure how well this would work, since my backends and frontends are a mix of P4's and xeons.
<br><br>What would be safest? <br><br>-Dave<br clear="all"><br>-- <br>David Frascone<br><br>I couldn't care less about apathy.