From owner-freebsd-ports@FreeBSD.ORG Wed Jul 19 17:12:37 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75D2016A4DF for ; Wed, 19 Jul 2006 17:12:37 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1494F43D45 for ; Wed, 19 Jul 2006 17:12:36 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 486C5352C; Wed, 19 Jul 2006 12:12:36 -0500 (CDT) Date: Wed, 19 Jul 2006 12:12:36 -0500 To: Matt Sealey Message-ID: <20060719171236.GA25814@soaustin.net> References: <007301c6ab52$c89d2e50$99dfdfdf@bakuhatsu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <007301c6ab52$c89d2e50$99dfdfdf@bakuhatsu.net> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-ports@freebsd.org Subject: Re: vim7 broken or not broken or? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 17:12:37 -0000 On Wed, Jul 19, 2006 at 11:45:42AM -0500, Matt Sealey wrote: > 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? Probably because you are not using the latest toolchain, such as the gmake import, and other things. It does not install/deinstall on the build cluster as a package. > 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". See below. > 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? After spending about 100 hours so far on package-building problems so far this month, I can assure you most emphatically that work is done to check whether or not these things build on the ports building cluster. The cluster environment attempts to install each port from scratch, including its dependencies as packages. This will catch many marginal cases that installing the port on a fully- (or nearly fully-) populated system will not catch. mcl