Vim and Vim-lite ports broken options

Jeremy Chadwick jdc at
Sun Jun 30 16:25:26 UTC 2013

(Please keep me CC'd as I'm not subscribed to -ports)

Yup, it's all broken.  I use vim-lite myself; the solution I found
is to drop this into /etc/make.conf:

.if ${.CURDIR:M*/editors/vim-lite}

Then "cd /usr/ports/editors/vim-lite ; make config", make sure
everything is de-selected, and it should be fine from there; the only
dependencies at that point will be libiconv and libtool.  This causes
the port to use the OPTIONS framework.

Do not ask me why this flag exists, as from what I can discern the
standard OPTIONS framework should suffice without "sub-knobs".  I get
the impression the driving force is to induce a non-interactive
behaviour, e.g. what BATCH "sort of" used to do (not sure if it still

There seems to be an unspoken reluctance upon the part of a single
committer who also happens to maintain very key/important ports.  A
similar situation happened with shells/bash, prompting shells/bash-devel
to be created/maintained by someone else.  There are public discussions
about that, multiple times:

The key/major discussion I cannot find right now (maybe it wasn't on -ports,
that's all I looked at, and only for the word "bash").

P.S. -- Unrelated to this matter, but the patch count for 7.3 is now up
to 1278 (i.e. the submitted patch count is up to 1278):!forum/vim_dev

Bram should be completely and totally ashamed (all while simultaneously
blabbing about "too many patches", "test 7.4 in May", yet there is no
such thing anywhere); a very sad state of affairs for such an important

| Jeremy Chadwick                                   jdc at |
| UNIX Systems Administrator       |
| Making life hard for others since 1977.             PGP 4BD6C0CB |

More information about the freebsd-ports mailing list