From owner-svn-ports-head@FreeBSD.ORG Thu Feb 20 08:39:41 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E6E991; Thu, 20 Feb 2014 08:39:41 +0000 (UTC) Received: from forward9l.mail.yandex.net (forward9l.mail.yandex.net [84.201.143.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B379D1348; Thu, 20 Feb 2014 08:39:40 +0000 (UTC) Received: from smtp4h.mail.yandex.net (smtp4h.mail.yandex.net [84.201.186.21]) by forward9l.mail.yandex.net (Yandex) with ESMTP id 1CF32E60D89; Thu, 20 Feb 2014 12:39:37 +0400 (MSK) Received: from smtp4h.mail.yandex.net (localhost [127.0.0.1]) by smtp4h.mail.yandex.net (Yandex) with ESMTP id 0F5822C345E; Thu, 20 Feb 2014 12:39:35 +0400 (MSK) Received: from unknown (unknown [178.76.234.16]) by smtp4h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id YZB4sEShxL-dZ1GuiOM; Thu, 20 Feb 2014 12:39:35 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: f7540c81-c8d1-4a14-a48e-ef6f7d272268 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1392885575; bh=zOaGSW9KmHHZwkJ8P7AxnKIqMSgbd4qI10f8jth68tc=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=PQhHX7qyFuvxwzWFRz+4dptNfqqG9OtcA5CTe46XWZAH4uIyn+o43l8Qr+KWDN8Ie qgG5jkiWkiNvNHMWK855IBo8roRSwqXJ5ADwARxU+a7oIvh72u1FA2/Yh2FLz9cgST o259MInkLWpHK9Dzf73MTAgfvMd94zkgzuwWoBok= Authentication-Results: smtp4h.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5305BF40.90003@yandex.ru> Date: Thu, 20 Feb 2014 12:39:28 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Baptiste Daroussin , Xin LI Subject: Re: svn commit: r345165 - head/devel/hgsvn References: <201402192351.s1JNplot033193@svn.freebsd.org> <20140219235746.GA1699@ithaqua.etoilebsd.net> In-Reply-To: <20140219235746.GA1699@ithaqua.etoilebsd.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Alex Kozlov , ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Feb 2014 08:39:41 -0000 Baptiste Daroussin wrote on 20.02.2014 03:57: [...] >> USE_PYTHON= yes >> USE_PYDISTUTILS=yes >> +USE_ZIP= yes >> PYDISTUTILS_AUTOPLIST= yes >> PLIST_SUB= VERSION=${PORTVERSION} PYVER=${PYTHON_VERSION:S/python//} > > Why readding USE_ZIP? while bsdtar can just extract it fine? Bapt, I already asked this, but got no response. ak@ made a patch to make USE_ZIP conditionally depend on unzip on a systems with old bsdtar. But it was never committed and pending portmgr@ approval. What the reason of this? What makes .zip so special, that we can't use this nice knob for it, but rather forced to construct pure ugliness with EXTRACT_SUFX? Thank you. PS. mat@ argued that it fails to deal with some of the zip-archives out there, but ak@ then said that he had no problems with any .zip's since libarchive 3.0.4. -- Regards, Ruslan T.O.S. Of Reality