From owner-freebsd-ports@FreeBSD.ORG Thu Apr 3 22:30:49 2014 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 ESMTPS id 45FCF676; Thu, 3 Apr 2014 22:30:49 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 076F07B0; Thu, 3 Apr 2014 22:30:49 +0000 (UTC) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 587A6BDC44; Fri, 4 Apr 2014 00:30:47 +0200 (CEST) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) by prod2.absolight.net (Postfix) with ESMTPA id 3733EBDC1F; Fri, 4 Apr 2014 00:30:47 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by atuin.in.mat.cc (Postfix) with ESMTP id 8037BD321A24; Fri, 4 Apr 2014 00:30:46 +0200 (CEST) Date: Fri, 04 Apr 2014 00:30:45 +0100 From: Mathieu Arnold To: marino@freebsd.org, freebsd-ports@freebsd.org, j.david.lists@gmail.com Subject: Re: Updating less-than-everything with poudriere & pkgng Message-ID: <4089E871513E3413EEEFA429@atuin.in.mat.cc> In-Reply-To: <533DBC8C.9040400@marino.st> References: <91FF893BBE05EEFA2894EED9@atuin.in.mat.cc> <891ACB1137F7FAFFFFAF9A3A@ogg.in.absolight.net> <533DBC8C.9040400@marino.st> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 22:30:49 -0000 +--On 3 avril 2014 21:54:52 +0200 John Marino wrote: | I don't think anybody is going to reprogram the logic of poudriere | though. This is just an academic discussion of what could be done, but | I doubt anybody wants to actually implement it due to the potential side | effects (and the (limited) gain vs the implementation cost). Yay, we've talked about this quite a lot, and there's the simple and always working way, but maybe somewhat overkill sometime, that poudriere is doing right now, and there is the way that *always* gets out *exactly* *right* what package to rebuild, and what package not to rebuild. That second way of doing things would be a monsterously beast of bugridden code, and take so much reverse engineering into each package to figure out what it needs it would certainly take more time in the end. -- Mathieu Arnold