From owner-freebsd-ports@FreeBSD.ORG Thu Nov 22 08:38:47 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 999DB16A41B for ; Thu, 22 Nov 2007 08:38:47 +0000 (UTC) (envelope-from maho.nakata@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by mx1.freebsd.org (Postfix) with ESMTP id 80FB913C46A for ; Thu, 22 Nov 2007 08:38:47 +0000 (UTC) (envelope-from maho.nakata@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so2364711rvb for ; Thu, 22 Nov 2007 00:38:34 -0800 (PST) Received: by 10.140.251.1 with SMTP id y1mr3640982rvh.1195689286424; Wed, 21 Nov 2007 15:54:46 -0800 (PST) Received: from localhost ( [134.160.214.85]) by mx.google.com with ESMTPS id k34sm49166rvb.2007.11.21.15.54.42 (version=SSLv3 cipher=OTHER); Wed, 21 Nov 2007 15:54:44 -0800 (PST) Date: Thu, 22 Nov 2007 08:54:31 +0900 (JST) Message-Id: <20071122.085431.129774588.chat95@mac.com> To: linimon@FreeBSD.org From: Maho NAKATA In-Reply-To: <200711210759.56913.linimon@FreeBSD.org> References: <474106CB.9060700@math.missouri.edu> <20071119.132430.232757505.chat95@mac.com> <200711210759.56913.linimon@FreeBSD.org> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: Maho NAKATA Cc: stephen@math.missouri.edu, freebsd-ports@freebsd.org, portmgr@FreeBSD.org Subject: Re: octave-forge on FreeBSD 7.0 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: Thu, 22 Nov 2007 08:38:47 -0000 From: Mark Linimon Subject: Re: octave-forge on FreeBSD 7.0 Date: Wed, 21 Nov 2007 07:59:56 -0600 > I'd rather see USE_GCC set unconditionally, so that INDEX will > be the same on 6 and 7. Me too. > Is there any hope of the software being updated? My concern is > that once we set this, we'll tend to forget about it later. Yes. IMHO, octave-forge should be merged into octave itself, and relese version of octave and corrsponding octave-forge is old. I think this is a temporal situation. Once octave will be updated octave-forge will also be updated, and I believe octave-forge will be built with gcc42. Thanks, -- Nakata Maho (maho@FreeBSD.org)