From owner-svn-ports-head@FreeBSD.ORG Thu Mar 27 16:39:19 2014 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 76F49B0C for ; Thu, 27 Mar 2014 16:39:19 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (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 5858F7A4 for ; Thu, 27 Mar 2014 16:39:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2RGdJvW045868 for ; Thu, 27 Mar 2014 16:39:19 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2RGdJVR045861 for svn-ports-head@freebsd.org; Thu, 27 Mar 2014 16:39:19 GMT (envelope-from bdrewery) Received: (qmail 9123 invoked from network); 27 Mar 2014 11:39:17 -0500 Received: from unknown (HELO roundcube.xk42.net) (10.10.5.5) by sweb.xzibition.com with SMTP; 27 Mar 2014 11:39:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 27 Mar 2014 11:39:17 -0500 From: Bryan Drewery To: Alexey Dokuchaev Subject: Re: svn commit: r347539 - in head: biology/genpak biology/rasmol cad/chipmunk databases/typhoon databases/xmbase-grok devel/asl devel/flick devel/happydoc devel/ixlib devel/p5-Penguin-Easy editors/axe ... Organization: FreeBSD In-Reply-To: <20140327130726.GD93483@FreeBSD.org> References: <201403082226.s28MQMtI079354@svn.freebsd.org> <20140327111602.GA57802@FreeBSD.org> <20140327130726.GD93483@FreeBSD.org> Message-ID: <8db20343037cfedce85801350a12fe4d@shatow.net> X-Sender: bdrewery@FreeBSD.org User-Agent: Roundcube Webmail/0.9.5 Cc: svn-ports-head@freebsd.org, Antoine Brodin , owner-ports-committers@freebsd.org, 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: Thu, 27 Mar 2014 16:39:19 -0000 On 2014-03-27 08:07, Alexey Dokuchaev wrote: > On Thu, Mar 27, 2014 at 01:46:53PM +0100, Antoine Brodin wrote: >> On Thu, Mar 27, 2014 at 12:16 PM, Alexey Dokuchaev wrote: >> > E.g. I've set a few of my ports free (that is, relinquished control over to >> > ports@) to let others do occasional updates or minor tweaks without having >> > to wait for me to approve their changes. It works well enough for simple >> > ports that are hard to damage by careless committing which had sadly become >> > quite popular recently. >> >> This was a mistake on your side, if you care enough about a port but >> don't want to update it (strange idea if the port is in a good shape), > > I do not want *not* to update it; I just don't want to prevent others > from > doing it as well. Surely it does not sound right for complex ports > (like > nvidia-driver), but it works well enough for simple ports that require > a > version bump or something like that once in a while. > >> you should keep yourself as a maintainer and add a comment like "Feel >> free to update this port without prior approval", or give >> maintainership >> to an active team that really cares about this port. > > The problem with this that we do not have an official way of stating > such > intents (apart from adding a comment to a port's Makefile, but that > would > add even more diversity to them which I'm trying to fight). > >> The ports tree is not the Museum of Antiquities. > > Many people (myself included) love Ports Collection because you often > can > find stuff that that is long gone (or never appeared) in any popular > Linux > distro. In that sense, it is not Museum of Antiquities, but an > ultimate > collection of available software that builds and probably works on > FreeBSD. > This is so awesome, I can't emphasize how well enough. I haven't need > to > google and ./configure && make && make install for hell of a time, > unlike > I still need to on GNU/Linux. > > Huge Port Collection is one of our winning points, not a nuisance. > > ./danfe /me pours fuel on the fire I agree completely with you. I don't understand why we remove ports that are working perfectly fine, except where broken or no upstream and there are security concerns. As a user I hate this. I still want older gcc and tcl. Portage has *32* versions of GCC while we have 4. For me, picking a development platform is all about which packages are available to test the portability of my code. Having ports@ allows anyone to update the port, but it does degrade the support for users. Users do need a contact for ports. We do need a way to nicely mark ports as free-for-all and yet still adopted by someone. Comments don't seem to cut it. This same thing applies to the teams too. How do we know some port in perl@ or games@ is *actually* maintained and not just in another "dead" bucket? And in fact there was a recent contentious discussion on this exact thing for perl@. A perl@ member placed a port there and was accused of throwing it at an unmaintained bucket. However, portmgr has discussed this recently and the direction of removing ports doesn't look to be changing anytime soon. -- Regards, Bryan Drewery