From owner-freebsd-ports@FreeBSD.ORG Sun Jun 27 19:43:52 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D0531065673 for ; Sun, 27 Jun 2010 19:43:52 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 4A2EB8FC19 for ; Sun, 27 Jun 2010 19:43:51 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o5RJhp6r063841; Sun, 27 Jun 2010 13:43:51 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o5RJhpcW063838; Sun, 27 Jun 2010 13:43:51 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 27 Jun 2010 13:43:51 -0600 (MDT) From: Warren Block To: Lev Serebryakov In-Reply-To: <381214039.20100627220400@serebryakov.spb.ru> Message-ID: References: <381214039.20100627220400@serebryakov.spb.ru> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (wonkity.com [127.0.0.1]); Sun, 27 Jun 2010 13:43:51 -0600 (MDT) Cc: freebsd-ports@freebsd.org Subject: Re: Early CONFLICTS detection is POLA viloation? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 19:43:52 -0000 On Sun, 27 Jun 2010, Lev Serebryakov wrote: > Hello, Freebsd-ports. > > I understand, that this change (ports/137855, bsd.port.mk:1.632) was made 6 months ago, but I've > noticed it only now (twice in one day!). > > Am I only person, who thinks, that this change is HUGE POLA > violation? > > PR says about "big tarball is downloaded and CONFLICTS are detected > after that," but I've have two more realistic scenarios, when early > conflict detection is VERY annoying. Thry are real-life scenarios, > occured today for me in a row. > > (1) I have `subversion' port installed, and want to `makesum' in > updated subversion-freebsd port directory (because I'm maintainer and > need to update port with new version, which have new tarball). OOPS. > I cannot even download new tarball -- confilct is detected. > > (2) I want upgrade perl from 5.8.x to 5.10.x. Type command: > > #portupgrade -rfo lang/petl5.10 perl-5.8.9_3 > > Ooops, confilct is detected, upgraid failed. GRRRR! > > > Maybe, early conflict detection should only print WARNING, and only > install target should be blocked by it, as everybody used for MANY > years? It's been mentioned before: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137855