From owner-freebsd-ports@FreeBSD.ORG Wed Jan 14 18:17:37 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 85D69CF1 for ; Wed, 14 Jan 2015 18:17:37 +0000 (UTC) Received: from udns.ultimatedns.net (ultimatedns.net [209.180.214.225]) (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 3B001768 for ; Wed, 14 Jan 2015 18:17:36 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t0EIGTVn078418 for ; Wed, 14 Jan 2015 10:16:29 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <54B696BF.5020901@FreeBSD.org> References: <2A3ABE9AE68B3CE8E1B7C1A1@ogg.in.absolight.net> <20150113163324.299F27E9@hub.freebsd.org> <20150114080033.GE33449@droso.dk> <20150114153427.63AD7C0A@hub.freebsd.org>, <54B696BF.5020901@FreeBSD.org> From: "Chris H" Subject: Re: BIND REPLACE_BASE option Date: Wed, 14 Jan 2015 10:16:29 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 18:17:37 -0000 On Wed, 14 Jan 2015 16:18:07 +0000 Matthew Seaman wrote > On 2015/01/14 15:34, Roger Marquis wrote: > > So one difference then would be that Poudriere determines which > > dependencies are run-time vs build-time and creates packages for those by > > default, is that correct? I can see how that might be convenient for > > packages with a large number of dependencies (like sssd) but it also > > seems like a lot of additional infrastructure simply to build binaries on > > one host to be used by many. > > Poudriere by definition will create packages for all of the build- and > run-depends, as it needs the build-depends packages itself in order to > build everything. It builds everything in temporary jails which it > installs all the needed dependencies to, and then destroys after that > package has been built. > > However, when you go to install a package from the repo, pkg(8) will > only pull down the run-time dependencies of whatever you choose to > install. That means there are a good chunk of packages you simply don't > need to have on your production servers any more. > > Yes, poudriere does a lot of stuff, but if you didn't use a central > builder, you'ld end up replicating all of that stuff onto every machine > you wanted to manage. Poudriere itself can run on a fairly modest > machine -- it depends on how many packages you need to build and how > quickly you want them. It's quite feasible to use poudriere for a > small-ish repo on a machine at night, when it is otherwise quiet, and > then use the same machine for something else during the day. This might be a good place to put some links to how-to's for common use-cases for poudriere. I see questions like this quite often on the lists, and in the forums. Anyone have one? --Chris > > Cheers, > > Matthew > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"