From owner-freebsd-questions@FreeBSD.ORG Fri Mar 19 20:35:16 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBDAE1065677 for ; Fri, 19 Mar 2010 20:35:16 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by mx1.freebsd.org (Postfix) with ESMTP id 880F98FC1E for ; Fri, 19 Mar 2010 20:35:15 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA11.westchester.pa.mail.comcast.net with comcast id v62r1d0040bG4ec5B8bGMs; Fri, 19 Mar 2010 20:35:16 +0000 Received: from comcast.net ([98.203.142.76]) by omta03.westchester.pa.mail.comcast.net with comcast id v8bE1d0061f6R9u3P8bFJb; Fri, 19 Mar 2010 20:35:16 +0000 Received: by comcast.net (sSMTP sendmail emulation); Fri, 19 Mar 2010 13:35:12 -0700 Date: Fri, 19 Mar 2010 13:35:12 -0700 From: Charlie Kester To: freebsd-questions@freebsd.org Message-ID: <20100319203512.GG265@comcast.net> Mail-Followup-To: freebsd-questions@freebsd.org References: <20100319170159.GB71392@slackbox.erewhon.net> <20100319200130.GE265@comcast.net> <86k4t8cbzi.fsf@blue.stonehenge.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <86k4t8cbzi.fsf@blue.stonehenge.com> X-Mailer: Mutt 1.5.20 X-Composer: VIM 7.2 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Elegant way to hack port source X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2010 20:35:16 -0000 On Fri 19 Mar 2010 at 13:06:41 PDT Randal L. Schwartz wrote: >>>>>> "Charlie" == Charlie Kester writes: > >Charlie> Whenever I modify a port like this, I usually make a copy of it under >Charlie> root's home directory and install it from there. That way, I can keep >Charlie> my copy of the portstree in complete synch with the official one, and >Charlie> there's no need to worry about updates quashing my changes. It also >Charlie> provides a quick-and-dirty way to see which ports I've modified. > >Isn't that also what /usr/ports/local is for? I think so. Hopefully somebody more knowledgeable than me will confirm or deny.