freebsd-skq/etc/portsnap.conf

# $FreeBSD$

# Default directory where compressed snapshots are stored.
# WORKDIR=/var/db/portsnap

# Default location of the ports tree (target for "update" and "extract").
# PORTSDIR=/usr/ports

# Server or server pool from which to fetch updates.  You can change
# this to point at a specific server if you want, but in most cases
# using a "nearby" server won't provide a measurable improvement in
# performance.
SERVERNAME=portsnap.FreeBSD.org

# Trusted keyprint.  Changing this is a Bad Idea unless you've received
# a PGP-signed email from <security-officer@FreeBSD.org> telling you to
# change it and explaining why.
KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330

# Example of ignoring parts of the ports tree.  If you know that you
# absolutely will not need certain parts of the tree, this will save
# some bandwidth and disk space.  See the manual page for more details.
#
# WARNING: Working with an incomplete ports tree is not supported and
# can cause problems due to missing dependencies.  If you have REFUSE
# directives and experience problems, remove them and update your tree
# before asking for help on the mailing lists.
#
# REFUSE arabic chinese french german hebrew hungarian japanese
# REFUSE korean polish portuguese russian ukrainian vietnamese

# List of INDEX files to build and the DESCRIBE file to use for each
INDEX INDEX-5 DESCRIBE.5
INDEX INDEX-6 DESCRIBE.6
INDEX INDEX-7 DESCRIBE.7
Add portsnap to the base system. This is a secure, easy to use, fast, lightweight, and generally good way for users to keep their ports trees up to date. This is version 0.9.4 from the ports tree (sysutils/portsnap) with the following changes: 1. The experimental pipelined http code is enabled. No seatbelts in -CURRENT. (^_^) 2. The working directory has moved from /usr/local/portsnap to /var/db/portsnap (as discussed on -arch two days ago). 3. Portsnap now fetches a list of mirrors (distributed as DNS SRV records) and selects one randomly. This should help to avoid the uneven loading which plagues the cvsup mirror network. 4. The license is now 2-clause BSD instead of 3-clause BSD. 5. Various incidental changes to make portsnap fit into the base system's build mechanics. X-MFC-After: 6.0-RELEASE X-MFC-Before: 5.5-RELEASE X-MFC-To: RELENG_6, RELENG_5, ports discussed on: -arch and several other places "yes please" from: simon, remko, flz, Diane Bruce thinks this is a great idea: bsdimp Hopes he didn't forget any files: cperciva 2005-08-08 20:10:06 +00:00			`# $FreeBSD$`

			`# Default directory where compressed snapshots are stored.`
			`# WORKDIR=/var/db/portsnap`

			`# Default location of the ports tree (target for "update" and "extract").`
			`# PORTSDIR=/usr/ports`

			`# Server or server pool from which to fetch updates. You can change`
			`# this to point at a specific server if you want, but in most cases`
			`# using a "nearby" server won't provide a measurable improvement in`
			`# performance.`
			`SERVERNAME=portsnap.FreeBSD.org`

			`# Trusted keyprint. Changing this is a Bad Idea unless you've received`
			`# a PGP-signed email from <security-officer@FreeBSD.org> telling you to`
			`# change it and explaining why.`
			`KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330`
Teach portsnap how to ignore unwanted parts of the ports tree. A line of the form "REFUSE foo" in portsnap.conf will result in parts of the tree matching "^foo" being (a) not extracted by "portsnap extract", (b) not updated by "portsnap update", and (c) not having any patches or new ports downloaded by "portsnap fetch" or "portsnap cron". The example shown in portsnap.conf demonstrates ignoring all the language categories. As mentioned in portsnap.conf.5, the use of an imcomplete ports tree is not officially supported; but this is something which many users have requested, so I'm adding it anyway. PR: bin/85619 (but not the patch provided therein) MFC after: 1 month 2005-09-06 19:28:37 +00:00
			`# Example of ignoring parts of the ports tree. If you know that you`
			`# absolutely will not need certain parts of the tree, this will save`
			`# some bandwidth and disk space. See the manual page for more details.`
Add a warning pointing out that incomplete ports trees are not supported and that users of REFUSE directives should update their entire ports tree before asking for help on the mailing lists. Requested by: kris MFC after: 3 days 2006-01-18 03:40:57 +00:00			`#`
			`# WARNING: Working with an incomplete ports tree is not supported and`
			`# can cause problems due to missing dependencies. If you have REFUSE`
			`# directives and experience problems, remove them and update your tree`
			`# before asking for help on the mailing lists.`
			`#`
Teach portsnap how to ignore unwanted parts of the ports tree. A line of the form "REFUSE foo" in portsnap.conf will result in parts of the tree matching "^foo" being (a) not extracted by "portsnap extract", (b) not updated by "portsnap update", and (c) not having any patches or new ports downloaded by "portsnap fetch" or "portsnap cron". The example shown in portsnap.conf demonstrates ignoring all the language categories. As mentioned in portsnap.conf.5, the use of an imcomplete ports tree is not officially supported; but this is something which many users have requested, so I'm adding it anyway. PR: bin/85619 (but not the patch provided therein) MFC after: 1 month 2005-09-06 19:28:37 +00:00			`# REFUSE arabic chinese french german hebrew hungarian japanese`
			`# REFUSE korean polish portuguese russian ukrainian vietnamese`
Add support for specifying which INDEX files to build via portsnap.conf. Requested by: brooks Reminded by: brooks, about halfway through his BSDCan talk 2008-05-17 16:26:27 +00:00
			`# List of INDEX files to build and the DESCRIBE file to use for each`
			`INDEX INDEX-5 DESCRIBE.5`
			`INDEX INDEX-6 DESCRIBE.6`
			`INDEX INDEX-7 DESCRIBE.7`