From owner-freebsd-ports Wed Nov 25 14:05:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15960 for freebsd-ports-outgoing; Wed, 25 Nov 1998 14:05:07 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from jade.chc-chimes.com (jade.chc-chimes.com [206.67.97.83]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15934; Wed, 25 Nov 1998 14:04:53 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: from localhost (billf@localhost) by jade.chc-chimes.com (8.8.8/8.8.8) with SMTP id RAA08631; Wed, 25 Nov 1998 17:04:37 -0500 (EST) (envelope-from billf@jade.chc-chimes.com) Date: Wed, 25 Nov 1998 17:04:37 -0500 (EST) From: Bill Fumerola To: Ian Struble cc: Bill Fumerola , freebsd-ports@FreeBSD.ORG Subject: Re: ports/8807 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No problem. What's important is that the port isn't broken for -CURRENT anymore. On Wed, 25 Nov 1998, Ian Struble wrote: > Ack! I totally spaced on cleaning up that makefile. I think i left them > in there hoping to ask a question before I submitted it, but whatever the > reason I'll be a little neater next time! > > Ian > > On Wed, 25 Nov 1998, Bill Fumerola wrote: > > > Synopsis: port was marked BROKEN=perl5 -- FIXED > > > > State-Changed-From-To: open-closed > > State-Changed-By: billf > > State-Changed-When: Wed Nov 25 12:11:34 PST 1998 > > State-Changed-Why: > > Added patch! Thanks! > > > > One nit though: Your patch of the Makefile patched a Makefile that had hashes in it. I assume this was your 'work' Makefile. Not a big deal, but just check your patches before you submit them. > > > > Either way, thanks for unbreaking this port. > > > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message