From owner-cvs-all@FreeBSD.ORG Sat Jan 5 02:08:08 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A5C416A473; Sat, 5 Jan 2008 02:08:08 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 3D93B13C43E; Sat, 5 Jan 2008 02:08:08 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 0812B8C113; Fri, 4 Jan 2008 20:08:08 -0600 (CST) Date: Fri, 4 Jan 2008 20:08:08 -0600 To: Doug Barton Message-ID: <20080105020807.GA19156@soaustin.net> References: <200801041328.m04DSp6h096405@repoman.freebsd.org> <477EB668.3090400@freebsd.org> <477EDCBC.2090402@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <477EDCBC.2090402@FreeBSD.org> User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) Cc: cvs-ports@FreeBSD.org, Pav Lucistnik , cvs-all@FreeBSD.org, Colin Percival , ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/ports-mgmt Makefile ports/ports-mgmt/pkg_cleanup Makefile pkg-descr ports/ports-mgmt/pkg_cleanup/files Makefile pkg_cleanup.1 pkg_cleanup.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2008 02:08:08 -0000 On Fri, Jan 04, 2008 at 05:26:20PM -0800, Doug Barton wrote: > Colin Percival wrote: > > Is there a standard policy for when a port's source code should be included in > > the ports tree instead of in a separate distfile which is fetched on demand? > > I actually do not know if there is a codified policy, but I have two > original works in the ports tree so I'll share my thought process. > > The first criterion I used was, "Is it directly related to FreeBSD, > and only FreeBSD?" There's never been a discussion of a policy IIRC. I suppose that if something is of significant size but is FreeBSD-only, it might be a candidate for our (underused) projects/ repo. mcl