From owner-freebsd-ports@FreeBSD.ORG Thu Sep 29 23:13:33 2011 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 75A4A1065670; Thu, 29 Sep 2011 23:13:33 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (cl-414.sto-01.se.sixxs.net [IPv6:2001:16d8:ff00:19d::2]) by mx1.freebsd.org (Postfix) with ESMTP id 287E78FC08; Thu, 29 Sep 2011 23:13:33 +0000 (UTC) Received: from orion.SpringDaemons.com (207.47.0.2.static.nextweb.net [207.47.0.2]) by mx0.deglitch.com (Postfix) with ESMTPA id 9C5E08FC2D; Fri, 30 Sep 2011 03:13:31 +0400 (MSD) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id 54FDA5C36; Thu, 29 Sep 2011 16:12:40 -0700 (PDT) Date: Thu, 29 Sep 2011 16:12:40 -0700 From: Stanislav Sedov To: Eitan Adler Message-Id: <20110929161240.461ceda8.stas@FreeBSD.org> In-Reply-To: References: <20110929084725.GN91943@hoeg.nl> <20110929094733.GS5495@droso.net> <20110929134626.8c019ef1.stas@FreeBSD.org> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Stanislav Sedov , freebsd-ports@freebsd.org Subject: Re: Instafix for FreeBSD ports brokenness on 10.0? 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: Thu, 29 Sep 2011 23:13:33 -0000 On Thu, 29 Sep 2011 17:40:36 -0400 Eitan Adler mentioned: > The ports tree can be very fickle and touching a large class of ports > requires multiple exp-runs. Attempting these types of changes > just prior to release adds a degree of risk which no one wants to accept. > Who don't want to accept this? Who is making this decision for everyone? > Affecting *every single port* is not a negligible risk. I can easily commit whatever I want to bsd.ruby.mk right now affecting all the ports (and nobody will say a word), but we can't do a conditional fix in bsd.port.mk? I'd say the first one poses much a higher risk (and I never did a single exp-run for that). Seriously, just look at the commits happening right now. Here's one example (the most recent commit, not picking up anything): 15:22 < CIA-28> [ports] glarkin * devel/Makefile: - Hook py-zope.interface to the build So now tell me how .if ${OSVERION} > SOMETHING do something .endif in bsd.port.mk is more risky then that particular commit which can potentially break devel/ for all OSVERSIONs. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments