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@
path to the interpreter such that configure can find it again.
Newer ruby and FLAVORS that aren't built by default will be
revisited post-5.5.
ok jeremy@ sthen@
longer needed. ok aja@ rpe@ also tested by brett@.
gsoares had a problem with no_x11 but I can't see why and can't
reproduce it, let me know if anyone else sees this.
for consistency with the gem/extconf ports.
Update non-gem/extconf ports that relied on the previous
default of ruby 1.8 to explicitly specify it.
OK ajacoutot@
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@
script to use "gtar" not "tar". This is not added as a run dep to avoid
pulling in extra dependencies, especially xz which requires gcc3+ so is
not available on some arch and is more difficult to build on others.
(There's a clear error message at runtime if gtar is unavailable.)
ok dcoppa@ ckuethe@
into MODRUBY_WANTLIB and using CONFIGURE_STYLE = ruby gem ext. Use the
lang/ruby module for all dependent ports, setting
MODRUBY_{BUILD,RUN}DEP=No if necessary.
ok landry, phessler, sthen
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.
