From owner-freebsd-current@FreeBSD.ORG Mon Oct 10 22:57:05 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 490A8106564A; Mon, 10 Oct 2011 22:57:05 +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 EC6248FC0A; Mon, 10 Oct 2011 22:57:04 +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 4B4CC8FC2D; Tue, 11 Oct 2011 02:57:03 +0400 (MSD) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id E01135C36; Mon, 10 Oct 2011 15:56:09 -0700 (PDT) Date: Mon, 10 Oct 2011 15:56:09 -0700 From: Stanislav Sedov To: Stanislav Sedov Message-Id: <20111010155609.9c053aa8.stas@FreeBSD.org> In-Reply-To: <20111010120419.9cfee3e9.stas@FreeBSD.org> References: <20111007230336.GB3051@laptop.levsha.me> <20111007164411.554ac9c0.stas@FreeBSD.org> <20111010120419.9cfee3e9.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: Mykola Dzham , current@freebsd.org, Stanislav Sedov , pp@gmail.com, "portmgr@freebsd.org" , jilles@freebsd.org, Chris Rees Subject: Re: ports on 10.0-CURRENT: r226027 is incorrect fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2011 22:57:05 -0000 On Mon, 10 Oct 2011 12:04:19 -0700 Stanislav Sedov mentioned: > On Sat, 8 Oct 2011 18:35:13 +0100 > Chris Rees mentioned: > > > > > Last I heard, portmgr explicitly disapproved of this fix-- have I missed > > something??? Erwin specifically said not to do it. > > > > Since when can anyone just commit stuff to bsd.port.mk, regardless of its > > location? > > > > This is a bad solution, please revert it or I will when I get back. We're > > going to end up being asked to support it on ports@ otherwise. > > > > You certianly missed something, including the rationale behind the portmgr@ > descision of not committing to the ports tree (!) bsd.port.mk. Go find > some useful work to do like deleting old ports or whatever. You might want > to consider deleting all mine ports, as I'm not going to support them anymore > (after you backed out this fix without approval I don't have a working ports > tree anymore on any of my 3 workstations). > Quoting myself. Sorry to all if this sounded rude, I might have overreacted. I didn't meant to be personal, it's just the whole situation is disappointing. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments