From owner-freebsd-security Sun May 14 8:16: 7 2000 Delivered-To: freebsd-security@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 2764C37BCCB for ; Sun, 14 May 2000 08:16:04 -0700 (PDT) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id LAA05695; Sun, 14 May 2000 11:15:52 -0400 (EDT) (envelope-from matt@zigg.com) Date: Sun, 14 May 2000 11:15:51 -0400 (EDT) From: Matt Behrens To: Doug Barton Cc: freebsd-security@FreeBSD.ORG Subject: Re: New packaging tool (was Re: Applying patches with out a compiler) In-Reply-To: <391E4BCC.6EA3DB59@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 13 May 2000, Doug Barton wrote: > I concur. I've always wondered why (info-)zip hasn't enjoyed more > popularity in the unix world. I used it extensively back when I ran > OS/2, and it has a lot of nice features. The reasons I've always avoided it: 1) until now, I've had this misconception (I don't know where it came from, but I just investigated it) that it did not handle UNIX permissions and ownerships (note that unzip does need a flag to restore ownerships); 2) every time I dig unzip out again it takes me several tries to remember just how to get recursion like I'm used to with tar. That said, I've used it to make up archives for Windoze boxes on several occasions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message