Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 May 2013 09:50:50 +0100
From:      Chris Rees <crees@FreeBSD.org>
To:        Kenta Suzumoto <kentas@hush.com>, "ports@freebsd.org" <ports@freebsd.org>,  "David O'Brien" <obrien@freebsd.org>
Subject:   Re: The vim port needs a refresh
Message-ID:  <CADLo83_AgAH0fARvtoYYmw5UEf7%2B3nEEs6U%2B6%2BhY8r0MbTkWFw@mail.gmail.com>
In-Reply-To: <20130524212318.B967FE6739@smtp.hushmail.com>
References:  <20130524212318.B967FE6739@smtp.hushmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 24 May 2013 22:23, Kenta Suzumoto <kentas@hush.com> wrote:
>
> Hello all. The editors/vim port is currently a mess and needs some changes.
>
> - It fetches almost 700 patches from what seems like a dial-up connection in AUSTRALIA.
>
> You might as well be downloading a 1080p movie from a rock in the north pole, because that's about how fast it is.
> This can be very easily avoided by putting all the patches into a single tarball and hosting it anywhere decent. I've
> seen someone in ##freebsd on freenode handing out a tarball with all the patches many times, and everyone asks
> "why isn't this the default? why is some random guy giving me distfiles?" etc. Seems like a no-brainer.
>
> - By default, it builds lots of gui stuff that certainly almost no one wants
>
> It almost seems like the vim-lite port should be renamed vim and the vim port should be renamed gvim. I had to
> google to come up with this solution, because I can't even disable that stuff in "make config" (another problem!)
>
> .if ${.CURDIR}=="/usr/ports/editors/vim"
> WITH_VIM_OPTIONS=yes
> WITHOUT_X11=yes
> .endif
>
> People shouldn't have to find this hack to be able to install vim normally (and no, telling them to use vim-lite isn't normal).
> I'm surprised that none of these changes have been made yet. I've heard it's "because the maintainer won't listen to reason"
> but I have no way to know if that's the case or not. I also heard bapt@ had an optionsNG patch that he wouldn't
> integrate into the port for some reason. Please, let's get this stuff fixed once and for all. None of it requires a large amount
> of work on anyone's part.

I'm very sad to talk of a fellow developer like this, but I'm afraid
the maintainer of vim is a contrarian who thinks he knows better than
everyone else on the matter.

For years, people have been begging him to get over his fear of
OPTIONS, and he sits in the way of progress against almost everyone's
wishes.

He has also impeded progress on the bash port, resulting in the
ridiculous situation where we now have two bash ports, where one will
do.  For historical reasons, people seem reluctant to confront him
about this, and he ignores all attempts to reason about it.

It's far beyond time to remove David O'Brien from MAINTAINER lines--
he doesn't do the job properly anyway; several PRs he's timed out on
for his ports:

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/177597

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/174965

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/175447

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/178462

Last time I timed him out on a PR I was subjected to a tirade from
him, with questionable justification, but I may process these too when
I have time.

Alternatively, perhaps we need an editors/vim-options port????

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_AgAH0fARvtoYYmw5UEf7%2B3nEEs6U%2B6%2BhY8r0MbTkWFw>