From owner-freebsd-qa  Thu May 30 12:47:29 2002
Delivered-To: freebsd-qa@freebsd.org
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by hub.freebsd.org (Postfix) with ESMTP
	id 188C137B40B; Thu, 30 May 2002 12:47:26 -0700 (PDT)
Received: from goblet.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g4UJljbq004020;
	Thu, 30 May 2002 15:47:46 -0400 (EDT)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [161.44.149.69])
	by goblet.cisco.com (Mirapoint)
	with ESMTP id ABF39165;
	Thu, 30 May 2002 15:47:16 -0400 (EDT)
Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1])
	by bmcgover-pc.cisco.com (8.11.6/8.11.6) with ESMTP id g4UJlGw82433;
	Thu, 30 May 2002 15:47:16 -0400 (EDT)
	(envelope-from bmcgover@bmcgover-pc.cisco.com)
Message-Id: <200205301947.g4UJlGw82433@bmcgover-pc.cisco.com>
To: bmah@acm.org
Cc: Hans Ottevanger <hansot@iae.nl>, qa@FreeBSD.ORG, re@FreeBSD.ORG,
	bmcgover@bmcgover-pc.cisco.com
Subject: Re: /usr/@LongLink is here again 
In-reply-to: Your message of "Thu, 30 May 2002 12:08:19 PDT."
             <200205301908.g4UJ8J3i042213@intruder.bmah.org> 
Date: Thu, 30 May 2002 15:47:16 -0400
From: "Brian J. McGovern" <bmcgover@cisco.com>
Sender: owner-freebsd-qa@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-qa.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-qa>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-qa>
X-Loop: FreeBSD.ORG

So perhaps its time to get up to a current GNU tar?

	-B

 > If memory serves me right, Hans Ottevanger wrote:
 > 
 > > It is caused by problems during installation with files that have names
 > > longer than 100 characters. In the 4.6 RC2 ports collection there are 17
 > > such files. In a recently cvsupped port tree there are 22.
 > 
 > Just to catch up people who aren't on the re list:
 > 
 > It's been suggested (by sobomax) that we could make the ports tree
 > tarball using cpio instead of tar.  The problem is that when I just
 > tried this, I wound up with a tarball that unpacks perfectly with cpio,
 > but our system tar chokes on it (it messes up long filenames).
 > Apparently "the GNU tar format" and "the POSIX tar format" aren't
 > exactly compatible when it comes to long filenames.  Our system tar
 > (which is an old GNU tar) claims to do POSIX tar in its manpage, but
 > this is a lie.  :-(
 > 
 > GNU tar from ports handles the long filenames just fine (the same way
 > that cpio does).
 > 
 > Bruce.
 > 
 > PS.  For those of you following along at home:
 > 
 >  (cd /usr && \
 >  find -E ports \! -regex '.*CVS(/.+)?' -a \! -regex 'ports/distfiles/.*' | \
 >  cpio -o -H ustar | \
 >  gzip > ${CD_DISC1}/ports/ports.tgz)
 > 
 > 
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-qa" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-qa" in the body of the message