From owner-freebsd-ports Fri Mar 3 5:20: 5 2000 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 819AF37C05F for ; Fri, 3 Mar 2000 05:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA45960; Fri, 3 Mar 2000 05:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 3 Mar 2000 05:20:02 -0800 (PST) Message-Id: <200003031320.FAA45960@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: assar@stacken.kth.se Subject: Re: ports/17036: working port for arla-0.31 Reply-To: assar@stacken.kth.se Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/17036; it has been noted by GNATS. From: assar@stacken.kth.se To: Will Andrews Cc: FreeBSD-gnats-submit@FreeBSD.ORG, thepish@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: ports/17036: working port for arla-0.31 Date: 03 Mar 2000 14:11:09 +0100 I wrote: > Will Andrews writes: > > About time! I was pretty intent on submitting a port removal request for > > this particular port, since I've never seen it build successfully before. > > Thanks. Having it there but not building didn't make me very happy > either... Sorry for being somewhat insistent on this, but I would like this to be fixed before the freeze on March 8th. So, what more is there's to do on this and want can I do to make sure it happens? The patches in ports/17036 should make everything build just fine. If there are any issues with those, please tell me and I'll try to solve them. Otherwise, just commit it. :-) /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message