Subject: Re: pax-as-tar extract to stdout patch
To: NetBSD Userlevel Technical Discussion List <tech-userlevel@NetBSD.ORG>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 06/16/2003 19:50:01
[ On Monday, June 16, 2003 at 18:27:51 (-0400), James Chacon wrote: ]
> Subject: Re: pax-as-tar extract to stdout patch
> Why? Are you trying to claim that no features in the tools beyond
> "standard" ones should be used in the build?
Partly, but more importantly I'm trying to say that the priority of APIs
used by tools used in the build should primarily be towards standards
based APIs such that standards based environments can support as much of
the build process as possible; and secondarily towards NetBSD enhanced
APIs such that those specialized tools used in the build will be
identical to standard NetBSD tools and such that the build can be fully
self-hosting with only the distributed tools (i.e. without $TOOLDIR).
To this end only 'pax' (and only the POSIX API of 'pax') should be used
for the puposes of handling portable archive files during the build
since it is more than sufficient for this purpose, and as well NetBSD
should (continue to) provide a standards-compatible 'pax' implementation.
Greg A. Woods
+1 416 218-0098; <email@example.com>; <firstname.lastname@example.org>
Planix, Inc. <email@example.com>; VE3TCP; Secrets of the Weird <firstname.lastname@example.org>