From owner-freebsd-questions@FreeBSD.ORG Fri Nov 15 10:48:47 2013 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1ECB2647 for ; Fri, 15 Nov 2013 10:48:47 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id DF0B52015 for ; Fri, 15 Nov 2013 10:48:46 +0000 (UTC) Received: from [96.28.178.143] ([96.28.178.143:55125] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 7D/F5-29861-70CF5825; Fri, 15 Nov 2013 10:48:40 +0000 Date: Fri, 15 Nov 2013 10:48:39 +0000 Message-ID: <7D.F5.29861.70CF5825@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-questions@FreeBSD.org Subject: Re: Source tree and ports tree on Linux file system? X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 10:48:47 -0000 > I think the /usr/src and /usr/ports tree can be "read only" > when they are "sourced" for building purposes. It's just > important where /usr/obj and the working directories for > stuff from /usr/ports are mapped to. If you have more than > enough RAM, you can make a memory disk and locate them > there. Otherwise, using a UFS partition (wherever it is > actually located) sounds better. The ports collection > allows setting a "working directory prefix" to move the > creation of files out of /usr/ports. Pay attention to > also deal with /usr/ports/distfiles (where the source > archives are stored) and /usr/ports/packages (if you're > going to build packages). In the case of a Linux file system, source tree and ports tree don't have to be read-only. But I figured it was safer to use UFS if possible, which is why I built subversion from pkgsrc on my USB-stick installation of NetBSD-current amd64. NetBSD 6.1_STABLE consistently hung on boot. I would need to keep changes to src and ports trees, so don't want to use memory disk if I don't have to. But I am reluctant to try to build ports when I can't connect to the Internet from FreeBSD on MSI Z77 MPOWER motherboard. Conceivably I could make fetchlist in FreeBSD and download from NetBSD, but that's too cumbersome and cloak-and-dagger. With more than one FreeBSD installation, both amd64 and i386, ports and src directories can be /usr/ports and /usr/src only on one computer, unless I download ports and src trees redundantly. I keep packages in /usr/packages and distfiles in $PORTSDIR/distfiles. I also have to keep separate WRKDIRs so builds for different installations don't collide, like WRKDIR=${.CURDIR}/work9amd64 and WRKDIR=${.CURDIR}/work9i386 For HEAD and 10-STABLE, I change 9 to 11 or 10. Tom