# 
# A "configuration" is a meta-project: a combination of various
# packages into a single source tree.
# 
# When you use configurations, a developer will typically create a
# working directory by checking out the root package (with 'arch get') 
# and then the component packages (with `arch build-config').
# 
# It's handy to have a browser for configurations -- to be able to quickly
# find out what revisions are the most recent for particular developer
# configurations.  In this file, you specify:
# 
# 	name -	a nickname for the configuration, used only the
# 		browser index
# 
#	package - the root package of the configuration.  This is the
# 		  package a developer would check out with `get'.
# 
# 	config - the configuration name.  This is the configuration a
#		 developer would pass to `build-config'.
# 
# Here is an example: some of the configurations in the regexps.com
# archive:
# 
# name			package				  config
# 
# devo.arch	lord@regexps.com--2002/dists--devo	regexps.com/devo.arch
# lord.arch	lord@regexps.com--2002/dists--lord	regexps.com/lord.arch
# 
# devo.ftp-utils	lord@regexps.com--2002/dists--devo	regexps.com/devo.ftp-utils
# lord.ftp-utils	lord@regexps.com--2002/dists--lord	regexps.com/lord.ftp-utils
# 
# devo.hackerlab	lord@regexps.com--2002/dists--devo	regexps.com/devo.hackerlab
# lord.hackerlab	lord@regexps.com--2002/dists--lord	regexps.com/lord.hackerlab
# 
# tag: Tom Lord Tue Feb  5 14:37:39 2002 ({browser}/=configs)
#
