From owner-freebsd-ports@FreeBSD.ORG Tue Jan 29 21:25:43 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6AE6FAB1 for ; Tue, 29 Jan 2013 21:25:43 +0000 (UTC) (envelope-from prvs=734b5b760=pschmehl_lists@tx.rr.com) Received: from ip-001.utdallas.edu (ip-001.utdallas.edu [129.110.20.107]) by mx1.freebsd.org (Postfix) with ESMTP id 2785C8B4 for ; Tue, 29 Jan 2013 21:25:42 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq0EACw9CFGBbgogVmdsb2JhbABEvw4DASICJCeCXQKBYxqIJKAVhlqKOpA4kChhA4hhoQ0 X-IronPort-AV: E=Sophos;i="4.84,561,1355119200"; d="scan'208";a="119982172" Received: from zxtm01.utdallas.edu (HELO utd71538.utdallas.edu) ([129.110.10.32]) by ip-001.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Jan 2013 15:24:34 -0600 Date: Tue, 29 Jan 2013 15:24:31 -0600 From: Paul Schmehl To: FreeBSD Ports List Subject: Problems with GITHUB pulls Message-ID: <309F46D9EBD01E6E224829E8@utd71538.campus.ad.utdallas.edu> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1465 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Paul Schmehl List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 21:25:43 -0000 I maintain the security/barnyard2 port. It pulls the software from git, which is the only place where it's available. Here's the relevant portion of the port's Makefile: USE_GITHUB= yes GH_ACCOUNT= firnsy GH_PROJECT= ${PORTNAME} GH_TAGNAME= master GH_COMMIT= 4dfdc80 The problem is, master's commit tag and md5 sum and size have changed. I *could* update the port by changing the commit tag and the distino file, but that's seems rather kludgy to me. The version hasn't changed. The developers simply fixed some problems in the software and then bumped master to the newer commit. Is that really the correct way to handle software at git? If so, am I going to be forced to update the port every time the developers make minor changes to a version? Is there a way for me to work around this problem so that the port version remains at the stable commit until the version actually gets bumped? GH_COMMIT is mandatory, so I can't leave that out. Yet the git tagname has changed. What's the best way to handle this? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell