From owner-freebsd-ports@FreeBSD.ORG Sun Dec 24 17:26:35 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 11E9016A412 for ; Sun, 24 Dec 2006 17:26:35 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id B8AF813C470 for ; Sun, 24 Dec 2006 17:26:34 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from working (c-71-60-174-60.hsd1.pa.comcast.net [71.60.174.60]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sun, 24 Dec 2006 12:16:30 -0500 id 0005641D.458EB5EE.0000469A Date: Sun, 24 Dec 2006 12:16:29 -0500 From: Bill Moran To: Josh Paetzel Message-Id: <20061224121629.169ecc1b.wmoran@collaborativefusion.com> In-Reply-To: <200612241053.03751.josh@tcbug.org> References: <200612241053.03751.josh@tcbug.org> Organization: Collaborative Fusion Inc. X-Mailer: Sylpheed version 2.2.10 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: Submitting a new port with dependancies not in the ports tree X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Dec 2006 17:26:35 -0000 Josh Paetzel wrote: > > I'm in the process of writing a port and it has a dependancy that's > not in the ports tree, so I'm porting that as well. My question is > what's the procedure in such a case? Should I submit them both as > part of the same pr? Obviously the one can't be committed without > the other. I don't know if there's any "official procedure" on this sort of thing. But I would submit them as two separate PRs, with references from the main to the dependency for tracking purposes. This way, if the dependency goes through easy and the main port raises some discussion, you can track them separately. -Bill