From owner-freebsd-ports@freebsd.org Thu Dec 15 17:43:19 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C1BEC813F1 for ; Thu, 15 Dec 2016 17:43:19 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3862D84; Thu, 15 Dec 2016 17:43:18 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7BE8928429; Thu, 15 Dec 2016 18:43:14 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id BBC9D28417; Thu, 15 Dec 2016 18:43:13 +0100 (CET) Subject: Re: The ports collection has some serious issues To: marino@freebsd.org, Torsten Zuehlsdorff , FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5852D631.4090208@quip.cz> Date: Thu, 15 Dec 2016 18:43:13 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 17:43:19 -0000 John Marino wrote on 2016/12/15 17:46: > [1] I've got it on my todo list to provide a new method that would > eliminate the "my builder just rebuilt 150 packages, but pkg(8) only > upgraded 2 packages" issue that some users don't want to see. It's a > lot more complicated than the conservative yet bulletproof approach > currently used by poudriere and synth. This is interesting case - we are running own Poudriere repo and I am fine with it. But I am a bit nervous when I know 150 packages was rebuilt and just 2 upgraded by pkg. In this case I want pkg to update (reinstall) all of them. If something changed so that 150 packages must be rebuilt why pkg doesn't reinstall them? Isn't it the possible place for problems after upgrade? Mirek