From owner-freebsd-questions@FreeBSD.ORG Sun Nov 2 15:18:01 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31C7616A4CE for ; Sun, 2 Nov 2003 15:18:01 -0800 (PST) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58B9143F75 for ; Sun, 2 Nov 2003 15:18:00 -0800 (PST) (envelope-from andi_payn@speedymail.org) Received: from [10.1.0.9] ([68.65.235.109]) by mta9.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031102231803.QGQK25728.mta9.adelphia.net@[10.1.0.9]>; Sun, 2 Nov 2003 18:18:03 -0500 From: andi payn To: William O'Higgins In-Reply-To: <20031102070050.GA28349@sillyrabbi.dyndns.org> References: <20031102070050.GA28349@sillyrabbi.dyndns.org> Content-Type: text/plain Message-Id: <1067815078.825.506.camel@verdammt.falcotronic.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 02 Nov 2003 15:17:58 -0800 Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: hacking broken ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 23:18:01 -0000 The rest of your question has been answered, but: On Sat, 2003-11-01 at 23:00, William O'Higgins wrote: > I found that there was only on reference to the filename in the > Makefile, so I changed it, and then I generated an MD5 on the file that > I had and put it into distfile. Instead of manually generating the MD5 and editing the distfile, you can fix the Makefile, delete the distfile, and do a "make makesum" and it will be built for you automatically. (Similarly, if for some reason the README.html has to be updated, just delete it an "make readme".) Otherwise, you're on the right track. Also, in addition to checking that nobody's already submitted this, reading the Porting handbook, and submitting your fix via send-pr, you should probably email the package maintainer directly. In fact, you might want to do this first--it's possible the maintainer is about to do this, or has already tried and run into problems that she can tell you about before you hit them, etc.--and/or maybe she knows where you can get the previous version of the tarball.