From owner-freebsd-ports@FreeBSD.ORG Fri Nov 8 23:50:39 2013 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BFA26639 for ; Fri, 8 Nov 2013 23:50:39 +0000 (UTC) (envelope-from jmk@wagsky.com) Received: from smtp.wagsky.com (smtp.allycomm.com [184.23.27.16]) by mx1.freebsd.org (Postfix) with ESMTP id A9F3828EF for ; Fri, 8 Nov 2013 23:50:39 +0000 (UTC) Received: from port5.pn.wagsky.com (port5.pn.wagsky.com [192.168.6.5]) by mailgw.pn.wagsky.com (Postfix) with ESMTP id D0E18C5; Fri, 8 Nov 2013 15:43:56 -0800 (PST) Message-ID: <527D773C.4070405@wagsky.com> Date: Fri, 08 Nov 2013 15:43:56 -0800 From: Jeff User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: pkg, poudriere, Different Options, Multiple Repositories -- Best Practices? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Nov 2013 23:50:39 -0000 The scenario I am trying to smooth out is that the vast majority of my machines all can use the same set of options on nearly all of the ports being built into packages. Using poudriere and pkg has made building within each jail a thing of the past, thankfully. The "cut to the chase" question is, "Is there a deterministic order for searching for packages among multiple repositories with pkg? If so, where is it documented?" The context: The tricky part is that one port here and there needs a different set of options for a specific machine/jail or two. For example, postfix can be trimmed down for most as it is just handling submission of locally generated mail and sending it off somewhere. However, the mail servers need auth and dovecot and their dependencies. I /could/ maintain complete repositories for each set of options, but when something with a lot of dependencies gets changed, it is a lot of rebuilding for just a couple ports that are different. I have read that pkg can handle multiple repositories, for example pkg.conf(5) and , and the thought would be that I would be that I build a "general" repository that has vast majority of packages, then "special" ones with, for example, postfix with dovecot, X11-enabled apps,... Then, I could specify the "special" version of the repo to be searched first, followed perhaps by another special one, then by the general one. That way postfix and friends would be picked up first, but more germane things like perl or python would be pulled from the general one (assuming it wasn't a dependency of the stuff in the "special" repo). The other question relates to poudriere -- "it" seems to want to build options files for everything under the sun, even if they are just "default" options (probably more the ports makefile than poudriere). I'd much prefer that what is in the poudriere.d/x-y-z directories are just the /changes/ to the default options. Is there any pre-packaged way to get the default options for a port and compare them to an options file's settings? Thanks! Jeff P.S. At least for me, poudriere works much, much more easily than I could ever get tinderbox to behave -- thanks to all that have contributed to its development!