From owner-freebsd-hackers Tue Jan 16 03:01:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA05206 for hackers-outgoing; Tue, 16 Jan 1996 03:01:20 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA05196 for ; Tue, 16 Jan 1996 03:01:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id AAA07649; Tue, 16 Jan 1996 00:44:22 -0800 To: Nate Williams cc: tnaggs@cddotdot.mikom.csir.co.za (Anthony Naggs), Hackers@freebsd.org Subject: Re: FBSD 2.1 In-reply-to: Your message of "Mon, 15 Jan 1996 22:46:05 MST." <199601160546.WAA03311@rocky.sri.MT.net> Date: Tue, 16 Jan 1996 00:44:22 -0800 Message-ID: <7647.821781862@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org Precedence: bulk > Do you want a library instead of just calling the zip/unzip utils and > parsing the output? Although I think the latter would be much slower, > it would avoid you having to GPL your package tools, and avoid > 'Yet-Another' GPL utility in the tree. That wouldn't save us anyway since we'd still need at least unzip in the tree. I figure if we're going to bring something like zip/unzip in, we might as well try to add some value to it. A library API to zip would be useful for a lot of things, I think. > Also, what kind of API would you like to see? You are the most familiar > with the package tools, so if you write up a quick 'this is what I'd > like to see API' then it would be easier for someone to know what is > expected. OK. I will do precisely that! Jordan