From owner-freebsd-questions@FreeBSD.ORG Tue Mar 25 09:06:13 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9A89601 for ; Tue, 25 Mar 2014 09:06:13 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5F0B8E19 for ; Tue, 25 Mar 2014 09:06:12 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s2P96Ae3006518; Tue, 25 Mar 2014 09:06:11 GMT (envelope-from freebsd@qeng-ho.org) Message-ID: <53314702.8030006@qeng-ho.org> Date: Tue, 25 Mar 2014 09:06:10 +0000 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: David Newman Subject: Re: Using pkg with build options References: <372190939.49499.1395582789284.JavaMail.mail@webmail12> <20140323150144.029c571e.freebsd@edvax.de> <532F15D8.10403@FreeBSD.org> <20140323185258.e389040f.freebsd@edvax.de> <5330C120.40905@networktest.com> <5330CB20.3090705@networktest.com> In-Reply-To: <5330CB20.3090705@networktest.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Mar 2014 09:06:13 -0000 On 25/03/2014 00:17, David Newman wrote: > On 3/24/14, 5:05 PM, Warren Block wrote: > >> On Mon, 24 Mar 2014, David Newman wrote: >> >>> I'm still quite confused over the migration to pkg. >>> >>> I have a mix of 9.2 and 10.0 machines. Most run at least one port >>> compiled with options. >>> >>> Is there a guide to moving these machines to pkg and poudriere? >> >> Are they all using ports now? > > Yes. > >> Then just switch each to the pkg database >> by adding WITH_PKGNG=yes and running pkg2ng to convert the package >> information. After that, continue to use ports as normal. pkg will >> keep track of them just like the old pkg_* programs did. > > Thanks, that's very helpful. > >> Using Poudriere to build binary packages of your own is not required. >> But if you want to do it, there's a short section on setting up >> Poudriere in the Handbook: >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-poudriere.html > > Part of the appeal of pkg is that package binaries install much faster > than waiting for 'portmaster -aD' to complete after updating the ports tree. > > However, if I understand that poudriere link, it would still build my > custom packages from ports, and thus there isn't much time savings. Correct? One thing to note is that by default poudriere uses its own copy of the ports tree, not /usr/ports, and that copy is updated by poudriere ports -u If like me you already use a cron job to update /usr/ports you can tell poudriere to use the existing ports tree by poudriere ports -c -F -f none -M /usr/ports -p default Last time I looked, this wasn't documented in the man page.