[27043] trunk/base/portmgr

[markd at macports.org]

macports-dev at lists.macosforge.org on Monday, July 16, 2007 at 10:59 AM
-0800 wrote:
>--- trunk/base/portmgr/mprsyncup	2007-07-16 15:35:59 UTC (rev 27042)
>+++ trunk/base/portmgr/mprsyncup	2007-07-16 17:59:44 UTC (rev 27043)
>@@ -5,11 +5,25 @@
> # release tag (as determined by the base/config/RELEASE_URL file) and a
>ports
> # tree from trunk (ToT), and then export and sync all of them to the
> # ${REPOROOT} location, wherefrom the rsync modules are fed to the `sync'
>-# and `selfupdate' routines in port(1).
>-# Read the base/portmgr/rsync.repos file for more information on both the
>-# necessary rsync modules and filesystem level paths, which this script
>-# bootstraps.
>+# and `selfupdate' routines in port(1). Read the base/portmgr/rsync.repos
>+# file for more information on both the necessary rsync modules and
>filesystem
>+# level paths, which this script bootstraps.
> #
>+# Whatever server uses this script to mirror the MacPorts rsync
>repositories
>+# should simply adapt the ${REPOROOT} path variable as necessary
>(keeping it
>+# in sync with the equally named variable in base/portmgr/rsync.repos)
>and
>+# install it on cron/launchd with a suitable periodicity, previously
>discussed
>+# with the portmgr@ team (macports-mgr at lists.macosforge.org).
>Repositories
>+# themselves are detailed & served by base/portmgr/rsync.repos, as
>stated above
>+# (that is, no manual intervention what-so-ever is needed, other than
>installing
>+# this script and adding the repositories detailed in
>base/portmgr/rsync.repos
>+# to a local rsyncd.conf file).
>+#
>+# Lastly, it is required of every 3rd party mirrors to keep track of
>this script
>+# and the base/portmgr/rsync.repos file and always maintain local copies
>in as
>+# close sync as possible. 

If I understood this better perhaps I could write it up in the new guide. 
When did this function become available?  What do we call it?  Remote
repository?  Is it basically an internal macports repository for the
enterprise?  Are the comments in mprsyncup and rsync.repos the only
documentation we have?

Mark