From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Sep 2 07:39:22 2014 Return-Path: Delivered-To: freebsd-ports-bugs@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 CE2562DB for ; Tue, 2 Sep 2014 07:39:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9BA571441 for ; Tue, 2 Sep 2014 07:39:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s827dMJP031704 for ; Tue, 2 Sep 2014 07:39:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193212] [stage] sysutils/bsdconfig Date: Tue, 02 Sep 2014 07:39:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: freebsd-ports@dan.me.uk X-Bugzilla-Status: Patch Ready X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2014 07:39:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193212 --- Comment #17 from Daniel Austin --- DEVELOPER=yes isnt required in the poudriere make.conf (in fact, I think it now actively complains about it). It's automatically set when doing a testport run, or bulk -t I believe the sample poudriere.conf file contains all the documentation you'd need to adjust any settings within it. The whole purpose of poudriere is to ensure that package builds do not pollute your system. Using ZFS is the easiest way as it just uses snapshots to maintain a clean jail for each build. Thr trouble with building ports on a live system is that you never know what installed ports/packages are going to affect the port you're building. Poudriere only ever builds a port with the base system plus any build/run_depends from the port in question. This is why poudriere testport logs are desired - it can do testing well beyond any standard live system. I'm not sure what issues you have with poudriere. As far as I'm concerned it's the perfect tool for testing builds, and it even lets me test against 8.4, 9.3, 10.0 and 11.0 (in both i386 and amd64) on the same machine. (and with some patches to qemu, you can even cross-build for some ARM targets) It's an excellent tool, and I wish we had been able to use it sooner. We used to have to use tinderbox which is nowhere near as useful as poudriere (and more annoying to setup!) -- You are receiving this mail because: You are the assignee for the bug.