From owner-freebsd-ports@FreeBSD.ORG Wed Nov 3 21:20:28 2004 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 1DCC516A556; Wed, 3 Nov 2004 21:20:28 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4D3143D1D; Wed, 3 Nov 2004 21:20:27 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 035E851448; Wed, 3 Nov 2004 13:22:37 -0800 (PST) Date: Wed, 3 Nov 2004 13:22:37 -0800 From: Kris Kennaway To: FreeBSD-CURRENT , ports@freebsd.org Message-ID: <20041103212237.GA10524@xor.obsecurity.org> References: <20041103210949.GA2329@laptoxa.toxa.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <20041103210949.GA2329@laptoxa.toxa.lan> User-Agent: Mutt/1.4.2.1i Subject: Re: native openoffice 1.1.3 package? 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: Wed, 03 Nov 2004 21:20:28 -0000 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 04, 2004 at 12:09:49AM +0300, Toxa wrote: > On ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-current/All/ > we have *-openoffice-1.1.3.tbz for many languages, but what about native > openoffice package build? Moreover, there's no ru-openoffice-1.1.3.tbz he= re.=20 > I'm just wondering about it because OpenOffice-1.1.3 doesn't compiles > neither on current nor on 5_stable The openoffice builds are problematic because they take so long, and they often time out on the package build cluster (i.e. when multiple OO builds end up being scheduled on the same machine). Fixing this properly will require some nontrivial work. Kris --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBiUwdWry0BWjoQKURAurbAJsHXovJZLvpoUi5/tLHMST7OIQAUQCggkPE IDXr8evXBMsbDe/UnG7aT50= =WM2z -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd--