<br><div><span class="gmail_quote">On 1/3/08, <b class="gmail_sendername">paul beard</b> <<a href="mailto:paulbeard@gmail.com">paulbeard@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div class="gmail_quote"><span class="q">On Jan 3, 2008 12:17 PM, Tabitha McNerney <<a href="mailto:tabithamc@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">tabithamc@gmail.com
</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all --<br><br>I would like to build, from source, on an Xserve running Leopard Server, a "standard" MacPorts system that could be deployed, in an organization, on numerous other Apple servers running the same version of the OS (
e.g. Leopard Server). In doing so I would use Apple's command-line tools (such as hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume that hangs off an external disk on my original Xserve which houses the MacPorts prefix (
e.g., /opt/local). I would then restore from this disc image to the additional machines slated to be the recipients of the original standard.<br></blockquote></span><div><br>I wonder if some combination of nfs (to mount your master repository), rsync (to update your local store) and some voodoo with a regex to update any files that are tied to hostnames (all your master builds might be tagged with "master" or "changeme").
</div></div></blockquote><div><br>Paul,<br><br>Appreciate the directional suggestion! Probably I could live without NFS and rsync, as I'd probably be ok with with cloning a master courtesy of the diskutil, hdiutil and asr tools on OS X. The regex is probably the way to go!
<br><br>Thanks,<br><br>T.M. <br> <br>[SNIP]<br><br><br></div></div><br>