From owner-freebsd-ports@FreeBSD.ORG Tue Apr 22 08:58:43 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 972B437B401 for ; Tue, 22 Apr 2003 08:58:43 -0700 (PDT) Received: from comrie.uwaterloo.ca (comrie.math.uwaterloo.ca [129.97.216.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id B640C43F3F for ; Tue, 22 Apr 2003 08:58:40 -0700 (PDT) (envelope-from mpatters@cs.uwaterloo.ca) Received: from comrie.uwaterloo.ca (localhost [127.0.0.1]) by comrie.uwaterloo.ca (8.12.6p2/8.12.6) with ESMTP id h3MFwdfG033467 for ; Tue, 22 Apr 2003 11:58:39 -0400 (EDT) (envelope-from mpatters@cs.uwaterloo.ca) Received: (from mpatters@localhost) by comrie.uwaterloo.ca (8.12.6p2/8.12.6/Submit) id h3MFwd2G033466 for freebsd-ports@freebsd.org; Tue, 22 Apr 2003 11:58:39 -0400 (EDT) X-Authentication-Warning: comrie.uwaterloo.ca: mpatters set sender to mpatters@cs.uwaterloo.ca using -f From: Mike Patterson To: freebsd-ports@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: CSCF Message-Id: <1051027119.75648.25.camel@comrie> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 22 Apr 2003 11:58:39 -0400 Subject: Building ports in a chrooted tree X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2003 15:58:43 -0000 I'm interested in creating a clean build environment for ports, something like the one used on bento. (See last paragraph for my reasons, and feel free to let me know if I've apparently been smoking substances of doubtful legality.) I've had a look through the porters handbook and it doesn't seem very clear the best way to go about this. Looking at bento, I found the two tarballs it uses to create a chrooted environment, except the problem is they appear to be for 4-stable or 5-current: my machine is RELENG_5_0. So, I assume that what I'll have to do is have a look at how /usr/src/release does it. Is that the best way to proceed? Did I miss some documentation somewhere? Is there a HOWTO anywhere for this? If not, should there be?) [0] I have a couple of reasons for this: currently my office has only a handful of FreeBSD machines, and the only one I can reasonably build ports on is my workstation. I'd like to be able to, for example, build apache+modphp without interfering with my apache+modssl+modperl installation. I also want to test a new port and don't want to have to pkg_delete -a on my workstation to make sure it builds cleanly. I've solved this problem in the past by simply creating a machine that mirrors my server environment and does all the ports building, but I don't have that luxury now. thanks, Mike -- There is only one thing in the world worse than being talked about, and that is not being talked about. - Oscar Wilde