From owner-freebsd-ports@FreeBSD.ORG Tue Mar 11 12:22:44 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D23D9AE; Tue, 11 Mar 2014 12:22:44 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0457CDD8; Tue, 11 Mar 2014 12:22:44 +0000 (UTC) Received: from [192.168.0.20] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 0F5A943B99; Tue, 11 Mar 2014 07:22:28 -0500 (CDT) Message-ID: <531EFFF8.2080604@marino.st> Date: Tue, 11 Mar 2014 13:22:16 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org, Eitan Adler Subject: Re: new USES=tar ? References: <20140311110549.GK6900@ithaqua.etoilebsd.net> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2014 12:22:44 -0000 On 3/11/2014 13:16, Eitan Adler wrote: > On 11 March 2014 07:05, Baptiste Daroussin wrote: >> Hi all, >> >> To be able to migrate most of the zip files to use bsdtar when they case we have >> added USES=zip[:infozip] for consistency I do plan to make the same kind of USES >> for every kind of archivers. I am puzzled on how to handle all the tar >> extensions what would your propose? >> >> One USES per extension? (USES=xz, USES=bzip2 etc?) >> >> or One USES=tar with arguments for extensions? > > Why does tar need an extension? why can't tar use the DISTFILE > itself? tar supports auto-detection of the format which it is > unzipping. For the automatic DISTFILES definition I assume. It does seem messy just to automatically determine DISTFILE file name though. John