Date: Fri, 12 May 2000 19:37:00 -0600 (MDT) From: Nate Williams <nate@yogotech.com> To: Wes Peters <wes@softweyr.com> Cc: Patrick Bihan-Faou <patrick@mindstep.com>, freebsd-security@FreeBSD.ORG Subject: Re: New packaging tool (was Re: Applying patches with out a compiler) Message-ID: <200005130137.TAA09188@nomad.yogotech.com> In-Reply-To: <391C9CBC.4E0ED8E5@softweyr.com> References: <Pine.NEB.3.96L.1000512123717.44824A-100000@fledge.watson.org> <E12qJVg-0005ow-00@xi.css.qmw.ac.uk> <107101bfbc60$aabeb350$040aa8c0@local.mindstep.com> <391C9CBC.4E0ED8E5@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I am currently working on a new version of pkg_*, which will bring a few > > features that I feel are missing. > > In my opinion, if we're going to replace the packaging system completely, > a good starting point might be to turn the PAX code, or something of > that nature, into a library and build on top of that. Not PAX. ZIP, since PAX and tar both require you to read to the end of the file to determine the contents of the file, and don't allow you to do random access I/O and pull out individual files. There are numerous advantages to using something like ZIP, including removing the requirement to 'unpack' the archive in a staging area, since we could now unpack it directly in it's installation location. ZIP also allows signatures, and we have lots of free software that we can leverage to implement the tools with it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005130137.TAA09188>