From owner-freebsd-hubs@FreeBSD.ORG Fri Oct 10 19:14:03 2008 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF5161065686 for ; Fri, 10 Oct 2008 19:14:03 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) by mx1.freebsd.org (Postfix) with ESMTP id 694BD8FC16 for ; Fri, 10 Oct 2008 19:14:03 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with SMTP; 10 Oct 2008 14:47:21 -0400 From: "Brian A. Seklecki" To: freebsd-hubs@freebsd.org Content-Type: text/plain Organization: Collaborative Fusion, Inc. Date: Fri, 10 Oct 2008 14:47:21 -0400 Message-Id: <1223664441.22435.320.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit Subject: CVSup distrib.self and static references to /home/ncvs X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2008 19:14:03 -0000 All: [Not sure if this is more of a freebsd-questions@ topic; didn't want to cross-post, though] So in setting up a new mirror, I noticed that the "distrib" collection is setup to write to dir ${BASEDIR}/prefixes/distrib.self, and distrib.self/ is a symlink to ../ Thus, prefixes/distrib/sup/*, which I guess is a set of server collection configuration files, becomes a subdir of ${BASEDIR}. Fair enough. For actual data, the fetch/update script included with FreeBSD, by default, fetches into ${BASEDIR}/prefixes/[collection], which is normally a symlink to /home/ncvs. Obviously, if you wanted to customize the file system layout, symlink arrangements, and the associated update script, that wouldn't be an issue. The problem seems to be that the the cvsupd(8) setup instructions tell the admin to run cvsupd(8) -s with ${BASEDIR}/sup.client and -c ${BASEDIR}, which then looks in ${BASEDIR}/sup for collection configuration files. Each of these files reference a prefix relative ${BASEDIR}/prefixes, but also have a static path to /home/ncvs. $ more sup/src-usrbin/releases cvs list=list.cvs prefix=prefixes/FreeBSD.cvs keywordprefix=/home/ncvs super=src-all So it seems that /home/ncvs is the default in: ports/net/cvsup-mirror/scripts/configure:ask_distrib Anyway, my point is this: Even if you change this locally in your client supfile and refresh your collections, you'd still have to maintain /home/ncvs as a symlink to wherever your local prefix=/ is and/or have a post-update script that recursively replaces instances of /home/nbsd. -- Brian A. Seklecki Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.