From owner-svn-ports-head@FreeBSD.ORG Mon Dec 2 14:13:44 2013 Return-Path: Delivered-To: svn-ports-head@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 67C871BF; Mon, 2 Dec 2013 14:13:44 +0000 (UTC) Received: from huppa.tuxaco.net (tuxaco.net [IPv6:2001:41d0:1:66c1::1]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 292131693; Mon, 2 Dec 2013 14:13:44 +0000 (UTC) Received: by huppa.tuxaco.net (Postfix, from userid 1001) id C70A922834; Mon, 2 Dec 2013 15:17:27 +0100 (CET) Date: Mon, 2 Dec 2013 15:17:27 +0100 From: Philippe =?iso-8859-1?Q?Aud=E9oud?= To: marino@freebsd.org Subject: Re: svn commit: r335281 - in head: . audio audio/gnump3d Message-ID: <20131202141727.GF71618@tuxaco.net> References: <201311301102.rAUB2I21004889@svn.freebsd.org> <20131202093409.GA71618@tuxaco.net> <529C5F05.6020706@marino.st> <20131202104324.GB71618@tuxaco.net> <529C689B.9050902@marino.st> <20131202131244.GC71618@tuxaco.net> <529C8C1F.7050802@marino.st> <20131202134921.GD71618@tuxaco.net> <529C91F2.6020004@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <529C91F2.6020004@marino.st> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: svn-ports-head@freebsd.org, Rene Ladan , svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 14:13:44 -0000 On Mon, 02 Dec 2013, John Marino wrote: > On 12/2/2013 14:49, Philippe Aud=E9oud wrote: > >=20 > > Ok, just calm down, every thing gonne be all right... I didn't challenge > > him, but I won't debate anymore, you don't look to be opened to a > > debate. > >=20 > > My personal think is : I was on week-end and i don't use computer on > > week-end. I guess this delete commit could wait 2 days. >=20 >=20 > Why should it? It was the date you defined. > Rene is right to assume that the port maintainer isn't intending to > delete the port in a timely fashion because it almost never happens. > Your desire to delete the port yourself on the expiration date is > exceptional. > It should not be exceptional: deleting a port is a part of a port's life. It's important to delete deprecated port to clean portstree. =20 >=20 > >> > >> This is the situation today. My position is that this is a bad policy. > >> I say we should not have to wait 2 weeks to unbreak a port and your > >> response is "wait up to 2 weeks to unbreak a port". Perhaps I > >> misunderstood you, but that's what I understood. > >> > >=20 > > And, if rules are not good, i break them? I disagree with highway code, > > and i should break it only because i'm not aware? >=20 >=20 > You are misrepresenting me. I follow the rules, but they are crappy > rules so I'm complaining about them. Rene did not break any rules that > I am aware of. (You conveniently did not show me where this "rule" is > documented, nor why you think port maintenance privilege extends past > the expire deadline). >=20 >=20 >=20 > > I'm not protective with my ports, I'm just applying rules. You can be > > disagree with rules but before breaking them and do what you want, you > > should talk to portmgr@ to change that. > >=20 > > And as you seem to have free time to mail on a wrong place debate, you > > should: > > 1- mail portmgr@ with your opinion and ask them to change current rules. > > 2- give a hand on closing PR for freebsd-port-bugs >=20 >=20 > To iterate: Nobody has broken any rules. What "rule" did Rene or I > break? To whom are you referring? >=20 > what does #2 have to do with anything? That is total random. >=20 It's not random at all. Helping cleaning PR queue is more useful that debating with me on a problem I don't really care. > I assume any active portmgr@ will see this thread. I don't need to > rehash it, not do I need to start simultaneous issues with them (I have > one pending already). >=20 You want to change something, talk to people who can change rules or take a place on portmgr@ I will close this thread for good: I don't care about this port deletion. Do what you want, I really really don't care about it. And at least, i asked something to rene@ not you. > Hint: If you don't respond, I'll stop responding too. :) Are we in a playground now?