From owner-freebsd-ports@FreeBSD.ORG  Sun Sep 21 23:18:33 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 1481816A4B3
	for <freebsd-ports@freebsd.org>; Sun, 21 Sep 2003 23:18:33 -0700 (PDT)
Received: from hueymiccailhuitl.mtu.ru (hueytecuilhuitl.mtu.ru
	[195.34.32.123])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 34DA143FE5
	for <freebsd-ports@freebsd.org>;
	Sun, 21 Sep 2003 23:18:32 -0700 (PDT)	(envelope-from sem@ciam.ru)
Received: from ciam.ru (ppp132-89.dialup.mtu-net.ru [62.118.132.89])
	by hueymiccailhuitl.mtu.ru (Postfix) with ESMTP
	id 8038A1358C8; Mon, 22 Sep 2003 10:18:26 +0400 (MSD)
	(envelope-from sem@ciam.ru)
Message-ID: <3F6E9433.7090205@ciam.ru>
Date: Mon, 22 Sep 2003 10:18:27 +0400
From: Sergey Matveychuk <sem@ciam.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.5b) Gecko/20030827
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rob Lahaye <lahaye@snu.ac.kr>
References: <3F6E73DD.2050605@snu.ac.kr>
In-Reply-To: <3F6E73DD.2050605@snu.ac.kr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-ports@freebsd.org
Subject: Re: How to patch and fix a broken port?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Sep 2003 06:18:33 -0000

Rob Lahaye wrote:
> I have never done this. So I apologize for my ignorant questions...
> 
> Last week I discovered that the molden port is broken in many ways
> (md5 sum wrong, install broken etc.). I reported it to the freebsd-ports
> mailing list and to the maintainer. I even attached a 'sort of' patch
> that fixed the build in a followup email, but never got any response,
> nor has the port been fixed.
> 
> So what to do with broken ports like that?
> 
> I can imagine that ports are broken and remain broken if nobody
> ever uses them or installs them. But as soon as a port is noticed
> as broken, it is necessary to get it fixed.
> 
> How is the general procedure to get this done?

Fill a PR and send it with send-pr(1). Don't forget Cc a port 
maintainer. After a while (a week or more) if the maintainer doesn't 
answer and doesn't fix the port ask here to commit your patch with "port 
maintainer timeout" reason.

Learn about PR from the handbook, porter's handbook and examples from 
GNATS database (http://www.freebsd.org/cgi/query-pr-summary.cgi).

Fill send-pr tidy and be sure you test the patch applying.

----
Sem.