Date: Wed, 19 Jul 2006 11:45:42 -0500 From: "Matt Sealey" <matt@genesi-usa.com> To: <freebsd-ports@freebsd.org> Subject: vim7 broken or not broken or? Message-ID: <007301c6ab52$c89d2e50$99dfdfdf@bakuhatsu.net>
next in thread | raw e-mail | index | archive | help
neko@mithrandir:/usr/ports$ portupgrade -f vim
** Port marked as IGNORE: editors/vim:
is marked as broken: does not compile on 4.X; use editors/vim6 =
instead
neko@mithrandir:/usr/ports$ vim --version
VIM - Vi IMproved 7.0 (2006 May 7, compiled Jul 5 2006 15:35:44)
Included patches: 1-4, 6-26, 29-31, 33-35
Compiled by neko@mithrandir.softwarenexus.net
neko@mithrandir:/usr/ports$ uname -a
FreeBSD mithrandir.softwarenexus.net 4.9-RELEASE FreeBSD 4.9-RELEASE #0: =
Mon Oct 27 17:51:09 GMT 2003 =
root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC i386
I got this version from ports the day it hit the tree, an upgrade from
vim6 (using the "vim" port directory). How come if it doesn't compile
on 4.X, I am running it now, compiled from the port?
A bunch of other stuff I have compiled is marked as broken too and no
major updates were posted. They just get marked as broken for 4.X or
"does not compile at all".
However I am having insane libtool problems with mod_python3 and =
mod_auth_pam2
which I cannot resolve. Does anyone actually check if these things =
really do
work or are they just being marked to close down the ports bug list as =
fast
as possible?
--=20
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007301c6ab52$c89d2e50$99dfdfdf>