CVE-2019-12735 Arbitrary Code Execution via Modelines
https://github.com/numirias/security/blob/master/doc/2019-06-04_ace-vim-neovim.md
"Beyond patching, it's recommended to disable modelines in the vimrc
(set nomodeline), to use the securemodelines plugin, or to disable
modelineexpr (since patch 8.1.1366, Vim-only) to disallow expressions in
modelines."
- add gtk3 flavour
- rework detection of incompatible flavours, less copy-and-pasting
when making changes
- remove the "huge" flavour, it wasn't linked to the build anyway, and
the option set by this was already used by default upstream
- remove bogus "CFLAGS/LDFLAGS=-pthread" setting for the gtk flavour
(very old - probably a remnant of uthread and not needed any more),
it was done as an override rather than addition, so the wanted CFLAGS
were not used for gtk builds.
- don't strip if this is a DEBUG build.
Changes:
* build -lang subpackage only for gui flavors so we can include
all documentation.
* install OpenBSD syntax files to share/vim/vimfiles, which is
version independent and in the runtimepath by default. This should
be used as target for vim plugin ports as it is version independent.
ok sthen@
a maintainer convenience target to allow this to be updated easily from
Mercurial) - this beats downloading 750+ individual patch files and
trying to force them to apply during the build (which is problematic
because some require GNU patch and some have problems even then...)
- clean up plists greatly.
- remove m68k gcc patch.
- add openbsd.vim for style(9) from gsoares@.
based on a diff from pirofti@, ok pirofti@ gsoares@
multi-packages are used when you have to build things together, but want
to separate the packages.
In this case, you have a bundle of things that do not even need to be
built together, that do not even share a MASTER_SITES, and were just bundled
because "they're related to vim".
This is deeply wrong. These files should be a separate port and packages.
Heck, they should be a separate port and several packages. Probably one
per-language.
