Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Mar 2014 11:39:17 -0500
From:      Bryan Drewery <bdrewery@FreeBSD.org>
To:        Alexey Dokuchaev <danfe@freebsd.org>
Cc:        svn-ports-head@freebsd.org, Antoine Brodin <antoine@freebsd.org>, owner-ports-committers@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org
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 ...
Message-ID:  <8db20343037cfedce85801350a12fe4d@shatow.net>
In-Reply-To: <20140327130726.GD93483@FreeBSD.org>
References:  <201403082226.s28MQMtI079354@svn.freebsd.org> <20140327111602.GA57802@FreeBSD.org> <CAALwa8kUkOWQ9fW2VpxsqA97B3antHGob=Hn35H%2BS93Kc1%2Bfdw@mail.gmail.com> <20140327130726.GD93483@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8db20343037cfedce85801350a12fe4d>