From owner-freebsd-ports@FreeBSD.ORG Wed Apr 11 02:25:56 2007 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 2D73416A402 for ; Wed, 11 Apr 2007 02:25:56 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.192.81]) by mx1.freebsd.org (Postfix) with ESMTP id 18F2513C45A for ; Wed, 11 Apr 2007 02:25:56 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from gimpy.tcbug.org (c-75-72-199-210.hsd1.mn.comcast.net[75.72.199.210]) by comcast.net (rwcrmhc11) with ESMTP id <20070411021444m11005hhjne>; Wed, 11 Apr 2007 02:14:44 +0000 Received: from gimpy.tcbug.org (localhost [127.0.0.1]) by gimpy.tcbug.org (Postfix) with ESMTP id A93368A040; Tue, 10 Apr 2007 21:15:05 -0500 (CDT) Received: (from jpaetzel@localhost) by gimpy.tcbug.org (8.13.8/8.13.8/Submit) id l3B2F4MY091962; Tue, 10 Apr 2007 21:15:04 -0500 (CDT) (envelope-from josh@tcbug.org) X-Authentication-Warning: gimpy.tcbug.org: jpaetzel set sender to josh@tcbug.org using -f Date: Tue, 10 Apr 2007 21:15:04 -0500 From: Josh Paetzel To: Vulpes Velox Message-ID: <20070411021504.GH57174@tcbug.org> References: <20070410021329.5f6865f8@vixen42> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070410021329.5f6865f8@vixen42> Cc: ports@freebsd.org Subject: Re: local ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Josh Paetzel List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2007 02:25:56 -0000 Vulpes Velox wrote: > I was just wondering what any one else thought of the idea of adding > a local directory to the ports tree and to the .cvsignore. This would > be a directory for users to put local custom ports. There's nothing to stop you from creating /usr/ports/local right now and just using it. You don't need a .cvsignore if you are using cvsup/csup, they ignore files that aren't in the cvs repo anyways. Of course if you are using portsnap that might be a different story, not sure how it handles updates... -- Thanks, Josh Paetzel