Juan Manuel Palacios <jmpp@macports.org> on Monday, July 16, 2007 at 1:29 PM -0800 wrote:
Thanks for inquiring about this, I was just about to write to you to request inclusion in the new guide ;-) The base/portmgr/mprsyncup and base/portmgr/rsync.repos files explain in their comments all that's needed to replicate our rsync mirrors locally, for instance on a server that wishes to supply local clients with faster sync/ selfupdate functionality off its own rsync server (not having to travel all the way to California if you're around the globe). Note that this is not exactly mirroring, as the example server would be doing the exact same thing rsync.macports.org is doing when setup with those two files, but independently of it (therefore "replicating").
Got it. Here is my description. Sound good? Are the terms I use ok? "You may setup an rsync replication server on your local network to minimize internet delay and bandwidth when performing MacPorts selfupdates. An rsync replication server pulls the latest rsync data (MacPorts base and port sources) from the remote MacPorts rsync mirrors via selfupdate, and then serves as the rsync source when rsync replication clients on the local network perform selfupdates." 1) What are the functional roles of the scripts mprsyncup and rsync.repos? As far as the server, I don't get REPOROOT as far the scripts. 2) Where do I set REPOROOT? mprsynup only has it in descriptive comments, and it isn't in "Paths we'll work on:", and rsync.repos has no single occurance where it can be set that I can find. Shouldn't there be one line somewhere with REPOROOT = /path/to/default/reporoot to uncomment? Ah wait! Is REPOROOT supposed to be named RSYNCROOT? 3) Does one set rsync.repos to run in cron also, along with mprsyncup? It says I need an rsyncd.conf? Where, how?
See what I have so far in "Using MacPorts" section 3.4. Mark