From owner-freebsd-ports@FreeBSD.ORG Wed Jun 20 12:17:21 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 288E316A468 for ; Wed, 20 Jun 2007 12:17:21 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail4out.barnet.com.au (mail4.barnet.com.au [202.83.178.125]) by mx1.freebsd.org (Postfix) with ESMTP id D78FC13C45B for ; Wed, 20 Jun 2007 12:17:20 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail4out.barnet.com.au (Postfix, from userid 1001) id 0CB5C37DEC8; Wed, 20 Jun 2007 22:17:20 +1000 (EST) X-Viruscan-Id: <46791ACF0000151D2E55CF@BarNet> Received: from mail4auth.barnet.com.au (mail4.barnet.com.au [202.83.178.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail4.barnet.com.au (Postfix) with ESMTP id D3639428AF7; Wed, 20 Jun 2007 22:17:19 +1000 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail4auth.barnet.com.au (Postfix) with ESMTP id 97F6D37DE9F; Wed, 20 Jun 2007 22:17:19 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 63C2721; Wed, 20 Jun 2007 22:17:19 +1000 (EST) Date: Wed, 20 Jun 2007 22:17:19 +1000 From: Edwin Groothuis To: Gabor Kovesdan Message-ID: <20070620121719.GB1558@k7.mavetju> References: <467918D0.3040900@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <467918D0.3040900@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Ports Subject: Re: Unused hashes from distinfo files X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2007 12:17:21 -0000 On Wed, Jun 20, 2007 at 02:08:48PM +0200, Gabor Kovesdan wrote: > there are RMD160 and SHA1 hashes in some ports' distinfo files. > Considering, that > 1, these kind of hashes were never official > 2, there's no PR for adding support for them $ SHA1=`which sha1` RMD160=`which rmd160` CHECKSUM_ALGORITHMS="rmd160 md5 sha256 sha1" make checksum (yes, we have a more-or-less pluggable checksum mechanism :-) > 3, SHA256 should be storng enough according to RMD160 and SHA1 Specially in combination with SIZE. Go for them (he said without any hats) Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/