From owner-freebsd-qa Thu May 30 12: 8:24 2002 Delivered-To: freebsd-qa@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 2CDC837B401; Thu, 30 May 2002 12:08:21 -0700 (PDT) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020530190820.PHWP11426.rwcrmhc51.attbi.com@bmah.dyndns.org>; Thu, 30 May 2002 19:08:20 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.3/8.12.3) with ESMTP id g4UJ8K7r042214; Thu, 30 May 2002 12:08:20 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.3/8.12.3/Submit) id g4UJ8J3i042213; Thu, 30 May 2002 12:08:19 -0700 (PDT) Message-Id: <200205301908.g4UJ8J3i042213@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020506 with nmh-1.0.4 To: Hans Ottevanger Cc: qa@FreeBSD.ORG, re@FreeBSD.ORG Subject: Re: /usr/@LongLink is here again In-reply-to: <3CF130DD.53BE43EF@iae.nl> References: <3CF130DD.53BE43EF@iae.nl> Comments: In-reply-to Hans Ottevanger message dated "Sun, 26 May 2002 21:00:45 +0200." From: bmah@acm.org (Bruce A. Mah) Reply-To: bmah@acm.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 May 2002 12:08:19 -0700 Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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