On Sun, 7 Aug 2005 12:22:29 +0300
Ossi Herrala <oherrala@...> wrote:
> On Sat, Aug 06, 2005 at 07:25:16AM -0700, Jon Buller wrote:
> > So the only thing to worry about is what to do on a stand-alone
> > build into /usr/local or something. And as much as I don't like
> > the look of the code below, it is probably pretty close to the
> > right thing to do, since the rest of the search/replace/what-should-
> > I-do infrastructure is not there.
> What is the reason asdf-install "requires" GNU tar to work properly?
> I did some untarring with GNU and BSD tar yesterday and diffing the
> output show that GNU tar puts leading slash "/" after directories
> where BSD tar doesn't do that.
bsdtar puts an x before every file name when it extracts files. And
SBCL relies on GNU tar's behaviour of not doing this.
> If it's about this, is there any better way to get around it than
> requiring every OS to have GNU tar?
Using pax (because it is POSIX), or running tar t before tar x to obtain
a file list. Or better yet use #'directory to see what new files got
LISP has survived for 21 years because it is an approximate local
optimum in the space of programming languages. - John McCarthy (1980)