Re: git-1.4.0 make problems

From: Junio C Hamano <junkio@cox.net>
Date: Jun 17, 2006, 20:56 UTC
Message-ID: <7vbqsra4d2.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <4493A810.6010706@lsrfire.ath.cx>

Rene Scharfe <rene.scharfe@lsrfire.ath.cx> writes:

Show 14 quoted lines

> | 1) The untar process creates a stray file "pax_global_header".
> | I am using GNU tar v1.13.22 and I get this message :
> |
> | ======================================================================
> | > tar jxf ~/u/source/git-1.4.0.tar.bz2
> | tar: pax_global_header: Unknown file type 'g', extracted as normal
> | file
> | ======================================================================
>
> You can ignore or delete that file.  It is a pax extended global header,
> containing the git commit ID as a comment.  GNU tar started supporting
> pax headers with version 1.13.93 (released 2004-02-23).  Version 1.13.22
> was released on 2001-08-29, by the way.  May I ask what operating system
> and version you are using?

I've been using (in my non-git related project aka day-job)

  git-tar-tree HEAD^{tree} $(PROJECT)-$(RELNAME) >$(PROJECT)-$(RELNAME).tar

to avoid this. Although all of my target machines have gtar that are recent enough so I do not need it, but when the tarball has version string in its name, there is not much point having the pax header to identify the contents (where the pax header shines is when the result does not have the version string in its name).

This might be a sensible thing to do for our dist target as well. The product of our dist target is for people who build from the source to bootstrap themselves (if they have git, then fetching the source using git is preferred anyway), as opposed to using pre-built binaries, so being as friendly as we can to different implementations of tar is a good thing.