From owner-freebsd-ports@FreeBSD.ORG Mon Mar 28 16:50:54 2005 Return-Path: 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 8DB1B16A4CE; Mon, 28 Mar 2005 16:50:54 +0000 (GMT) Received: from mail.logixonline.com (mail.logixonline.com [216.201.128.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C17B43D2F; Mon, 28 Mar 2005 16:50:54 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from [127.0.0.1] (unknown [216.201.253.131]) by mail.logixonline.com (SMTPd) with ESMTP id 1FE105C7E4; Mon, 28 Mar 2005 10:50:54 -0600 (CST) Message-ID: <424835EB.8010208@FreeBSD.org> Date: Mon, 28 Mar 2005 08:50:51 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Palle Girgensohn References: <00D88C763E4197939796E7C1@palle.girgensohn.se> In-Reply-To: <00D88C763E4197939796E7C1@palle.girgensohn.se> X-Enigmail-Version: 0.90.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: portmgr@freebsd.org Subject: Re: gettext X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 16:50:54 -0000 Palle Girgensohn wrote: > gettext is at 0.14.3, we still have 0.14.1. Are there good reasons for > lagging, or is it just that noone stepped forward and made the upgrade. > I do realize it requires a great deal of testing... :) Y'all just answered yourself :) Something to look to as soon as 5.4-RELEASE is out the door -- changing stuff required by half the ports tree a week or so before a freeze is insanely dangerous.. > Also, I got no response on the thought of splitting the gettext port > into -runtime and -tools, as suggested by the gettext folks, so > apparently noone considered it for the freebsd port. Is it a good idea, > or would it just be a nuisance? Thoughts, anyone? It's an absolute royal pain in the arse. On those systems where it is split into seperate items, I simply find myself adding them both in. The saving of a little bit of space, for the major upheaval in dependencies elsewhere in the tree, is simply not worth the pain. -aDe