From owner-cvs-all@FreeBSD.ORG Sun Jan 3 15:29:33 2010 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 733861065696 for ; Sun, 3 Jan 2010 15:29:33 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id C16D28FC1B for ; Sun, 3 Jan 2010 15:29:32 +0000 (UTC) Received: (qmail 28592 invoked by uid 399); 3 Jan 2010 15:29:32 -0000 Received: from localhost (HELO ?192.168.0.110?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 3 Jan 2010 15:29:32 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B40B7DE.7010703@FreeBSD.org> Date: Sun, 03 Jan 2010 07:29:34 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Joe Marcus Clarke References: <201001022211.o02MBMSn045154@repoman.freebsd.org> <4B402298.7040202@FreeBSD.org> <1262502385.16768.134.camel@shumai.marcuscom.com> In-Reply-To: <1262502385.16768.134.camel@shumai.marcuscom.com> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/archivers/file-roller Makefile ports/archivers/file-roller/files patch-src_fr-command-zip.c 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: Sun, 03 Jan 2010 15:29:33 -0000 Joe Marcus Clarke wrote: > On Sat, 2010-01-02 at 20:52 -0800, Doug Barton wrote: >> Isn't this bass-ackwards? Is there some functionality from unzip that >> this port needs that the version now in the base does not provide? If >> that's the case, can someone make that issue known so that interested >> parties can address it? > > There are two issues. The first is a lack of zipinfo. The unzip port > includes the zipinfo binary which can be invoked via unzip by passing > the -Z argument (i.e. unzip -Z is equivalent to calling zipinfo). > > The other major feature lacking in /usr/bin/unzip is password support. > The unzip port supports password-encoded archives (via the -P argument), > and the base version does not. > > If both of these issues get addressed, the base unzip would be fine. > Without the fixes, file-roller is useless when it comes to zip archives. That makes sense, thanks. -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso