From owner-freebsd-ports@FreeBSD.ORG  Thu Jul 28 21:31:11 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: 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 4DFF616A41F
	for <ports@freebsd.org>; Thu, 28 Jul 2005 21:31:11 +0000 (GMT)
	(envelope-from pauls@utdallas.edu)
Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C17F143D46
	for <ports@freebsd.org>; Thu, 28 Jul 2005 21:31:08 +0000 (GMT)
	(envelope-from pauls@utdallas.edu)
Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28])
	by smtp1.utdallas.edu (Postfix) with ESMTP id 2F5AF388D94
	for <ports@freebsd.org>; Thu, 28 Jul 2005 16:31:08 -0500 (CDT)
Date: Thu, 28 Jul 2005 16:31:08 -0500
From: Paul Schmehl <pauls@utdallas.edu>
To: ports@freebsd.org
Message-ID: <47ECFCB8BE498CEAB57757D7@utd59514.utdallas.edu>
In-Reply-To: <790a9fff050728142793c7588@mail.gmail.com>
References: <C3B81AFDB8A5DFB5AB566CC4@utd59514.utdallas.edu>
	<42E81050.7090305@cs.tu-berlin.de>
	<66A226C3557B48ED535E3FED@utd59514.utdallas.edu>
	<20050727230523.GB54954@isis.sigpipe.cz>
	<20050728154248.GA943@zi025.glhnet.mhn.de>
	<20050728164111.GA66015@isis.sigpipe.cz>
	<42E917BA.10406@exit.com>	<FACB47A35BF38243FBC04766@utd59514.utdallas.edu>
	<790a9fff050728142793c7588@mail.gmail.com>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 
Subject: Re: New port with maintainer ports@FreeBSD.org [was: Question about
 maintainers]
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
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: Thu, 28 Jul 2005 21:31:11 -0000

--On Thursday, July 28, 2005 16:27:21 -0500 Scot Hetzel 
<swhetzel@gmail.com> wrote:
>
> You wouldn't have to take on an additional challenge if one of the
> dependant ports is broken for a port your creating, what you could do
> is:
>
>   1. if MAINTAINER is not ports@, send a message to the MAINTAINER of the
> port   2. Send a PR for the port with a description of the breakage and a
> build.log containing the error
>   3. Same as 2, but you also correct the problem in the port, and
> include a Patch in the PR
>   4. Same as 3, and also ask to take maintainership if MAINTAINER is
> ports@.   5. Send a message to ports@ to see if anyone else had a problem
> with that port, and a if they have a solution
>
Thanks, Scot.  That's helpful to know.  I wasn't aware, for example, that 
anyone could submit PRs for a broken port.

Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/ir/security/