From owner-cvs-all@FreeBSD.ORG Sat Dec 24 19:10:34 2011 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 CB5F9106564A; Sat, 24 Dec 2011 19:10:34 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.49.45]) by mx1.freebsd.org (Postfix) with ESMTP id 243C78FC1A; Sat, 24 Dec 2011 19:10:30 +0000 (UTC) Received: by syn.atarininja.org (Postfix, from userid 1001) id 7B2A75C2E; Sat, 24 Dec 2011 14:10:29 -0500 (EST) Date: Sat, 24 Dec 2011 14:10:29 -0500 From: Wesley Shields To: Chris Rees Message-ID: <20111224191029.GA86653@atarininja.org> References: <201112181617.pBIGHWZM006457@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: cvs-ports@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/devel/git Makefile pkg-plist X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: **OBSOLETE** CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Dec 2011 19:10:34 -0000 On Wed, Dec 21, 2011 at 08:51:29PM +0000, Chris Rees wrote: > On 18 December 2011 16:17, Wesley Shields wrote: > > wxs ? ? ? ? 2011-12-18 16:17:32 UTC > > > > ?FreeBSD ports repository > > > > ?Modified files: > > ? ?devel/git ? ? ? ? ? ?Makefile pkg-plist > > ?Log: > > ?Switch to installing contrib files using COPYTREE_BIN instead of > > ?COPYTREE_SHARE. The documentation in the hooks says you should set > > ?executable permissions on the hook before setting it up in a repository, > > ?but if you update git the permissions get reset. Just install the entire > > ?contrib directory with executable bit set. > > > > ?What we really need is a "COPYTREE_ASIS" that just leaves the permissions as > > ?they are. > > > > ?Note I am intentionally not bumping PORTREVISION as this is a minor change > > ?and this port gets updated fairly regularly. > > Since we talked about this a few days ago I've been thinking, and just > noticed how ports-mgmt/tinderbox handles that use case with ${CP} > -R... I very well might switch to using this in the next update. Thanks! -- WXS