Ignore:
Timestamp:
Jul 16, 2007, 5:59:44 PM (13 years ago)
Author:
jmpp@…
Message:

Clarify instructions to replicate MacPorts rsync repositories on 3rd party servers,
emphasazing both base/portmgr/mprsyncup & base/portmgr/rsync.repos should be kept in
close sync among themselves and with their "official" copies in our svn.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/base/portmgr/rsync.repos

    r26489 r27043  
    33# maintained by the base/portmgr/mprsyncup script.
    44#
    5 # Two main modules are supplied for current installations off trunk and
    6 # two for backwards compatibility (legacy DarwinPorts namespace). Assuming
     5# Two main modules are supplied for current installations off the relase barnch
     6# and two for backwards compatibility (legacy DarwinPorts namespace). Assuming
    77# a REPOROOT path of /Volumes/data/rsync/macports/, this file is organized
    88# in the following four modules and filesystem level paths (server side):
     
    1313# ${REPOROOT}/release: holding a ports tree, exported from a checkout of svn's
    1414# trunk/dports dir (ToT), and the current release base dir, as determined by
    15 # the base/config/RELEASE_URL file read by the base/portmgr/mprsyncup
    16 # script;
     15# the base/config/RELEASE_URL file that's read by base/portmgr/mprsyncup;
    1716#
    1817# ${REPOROOT}/trunk: holding an export of a checkout from svn's trunk/base
     
    4342#
    4443#
    45 # Whatever server uses this file should simply add the modules listed here to
    46 # an already tailored rsyncd.conf file, as no other particular config options
    47 # are supplied. Repositories themselves are created and maintained by the
    48 # base/portmgr/mprsyncup script, as stated above (that is, no manual
    49 # intervention what-so-ever is needed, other than adding the repos to the local
    50 # rsyncd.conf file).
     44# Whatever server uses this file to mirror MacPorts rsync repositories
     45# should simply adapt the ${REPOROOT} path variable as necessary (keeping
     46# it in sync with the equally named variable in base/portmgr/mprsyncup)
     47# and add the listed modules to an already tailored rsyncd.conf file,
     48# as no other particular configuration options are supplied. Repositories
     49# themselves are created and maintained by base/portmgr/mprsyncup, as stated
     50# above (that is, no manual intervention what-so-ever is needed, other than
     51# adding the repositories to the local rsyncd.conf file and installing
     52# base/portmgr/mprsyncup on cron/launchd).
     53#
     54# Lastly, it is required of every 3rd party mirrors to keep track of this script
     55# and the base/portmgr/rsync.repos file and always maintain local copies in as
     56# close sync as possible.
     57#
    5158#
    5259# Created by Juan Manuel Palacios,
Note: See TracChangeset for help on using the changeset viewer.