The main goal is to pick up patch 1379:
Problem: Curly braces expression ending in " }" does not work.
Solution: Skip over white space when checking for "}". (closes#6634)
PR: 248504
Submitted by: p5B2E9A8F t-online de
Vim will link against libcanberra if it's present, leading to an
undeclared link and breakage risk if canberra is removed. It only really
makes sense for it to do this during a gnome build, so explicitly
enable it there and disable it elsewhere.
PR: 245460
Reported by: Andy Mender
MFH: 2020Q2
While here, restrict ctags patching attempts to only the files that
will need to be patched. This prevents the creation of dozens of
.orig files that are identical to the "patched" versions.
The error message (in poudriere) is as follows:
====> Running Q/A tests (stage-qa)
Error: '/usr/local/bin/python' is an invalid shebang you need USES=shebangfix for 'share/vim/vim82/tools/demoserver.py.bak'
r522484 adds a new REINPLACE_CMD check which is enabled when DEVELOPER=yes. It
does not respect REINPLACE_ARGS (-i ''), thus runtime/tools/demoserver.py.bak is
generated. Vim installs everything in runtime/tools [1] which fails in stage-qa
for invalid shebang.
This workaround uses USES=python:env. It will replace the shebang with default
python (/usr/local/bin/python3.7).
[1] from src/Makefile:
# install the runtime tools
$(INSTALL_DATA_R) $(TOOLSSOURCE)/* $(DEST_TOOLS)
PR: 243961
Reported by: salvadore
Submitted by: sunpoet (myself)
Approved by: adamw (maintainer)
When python is built with DEBUG, vim fails to build. In fixing this
case, note that vim will now fail to build if python or vim is build
with DEBUG and the other isn't.
This also highlighted that python support is being kludged. The
PYTHON2 and PYTHON3 options have been combined into a single PYTHON
option that builds with the default python. Consequently, it is no
longer possible to build vim with both py2 and py3 support. I can't
name any modern high-usage python-based plugin that requires 2.7,
so hopefully this only messes up things for a very small minority.
Thanks to koobs for the prompt to combine these options. I've been
wanting to do this for a while now.
PR: 243606
Submitted by: novel
Most systems are able to build vim in parallel most of the time.
The dependency chain in the Makefiles are a spaghetti mess and
concurrency is broken with some frequency, so it just isn't
feasible for it to be on by default.
It does shave quite a bit of time off the build (and I have had
.undef MAKE_JOBS_UNSAFE in Makefile.local for years), so now
there's an option. It's off by default.
PR: 243109
Reported by: glewis
Some big changes in this update:
* Patchlevel 1439
* Default python is now 3.x instead of 2.x [1]
* Expose DEFAULT_VIMRC option (on by default) to vim-tiny
Also, many changes to the default vimrc. Any changes necessarily risk
contention, but then I remembered that I actually maintain editors/vim,
so here we are. The idea here is that Vim, by default, behaves like Vi,
and people who install the Vim port do so because they DON'T just want
Vi. I've enabled features that are basic quality-of-life settings for
me, and that I hope will be ideal for most end-users.
Important changes in the default vimrc:
* Don't install gvimrc at all. gvim should load $ETCDIR/vimrc anyway. I
can't test gvim locally, so someone please let me know if I broke it.
* Turn on autoindent
* Disable console bells entirely. Console bells are terrible.
* Enable incsearch: highlights search results as you type them
* ^L clears search highlights while redrawing the screen
* Assume fast terminal by default
* Explain every setting in comments
Many of these settings are modeled after the defaults in NeoVim, which
really got it right. I want our default vimrc to be usable and ideal,
so please let me know if anything doesn't work for you, or if you have
other settings you'd like to see changed in the default.
In particular, please let me know if I broke gvim by removing the gvimrc!
PR: 235142 [1]
Submitted by: John W. O'Brien [1]
After discussion on freebsd-ports@, switch the default UI toolkit
from GTK2 to GTK3. There isn't a huge visual difference, so it's
more predicated on the idea that people are more likely to have
GTK3 already installed for other things.
Previously, we patched in the names of all the python binary versions, but
I have been doing a terrible job of keeping them up-to-date. Instead, just
tell vim's configure script the path to the binary we're using.
This will fix building against python 3.7.
PR: 230675
Reported by: Kamigishi Rei
MFH: 2018Q3
Upstream used to distribute protocol headers as separate packages, but has
decided to merge those to a common package, named xorgproto. This update
tracks that change.
* Add a new port, x11/xorgproto, with are protocol headers for xorg.
* Hook the new protocol port to the build and to infrastructure in
bsd.xorg.mk.
* Update all ports with a dependency on any of the old *proto packages to
instead depend on xorgproto. Bump portrevision.
* Delete the old *proto packages, update MOVED.
PR: 230023
Submitted by: zeising
Approved by: portmgr (antoine)
exp-run by: antoine