From owner-freebsd-ports@FreeBSD.ORG  Tue Aug  3 15:08:59 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B229A16A4CE; Tue,  3 Aug 2004 15:08:59 +0000 (GMT)
Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 72AEC43D31; Tue,  3 Aug 2004 15:08:59 +0000 (GMT)
	(envelope-from dgilbert@daveg.ca)
Received: by ox.eicat.ca (Postfix, from userid 66)
	id 7D6B9C26F; Tue,  3 Aug 2004 11:08:58 -0400 (EDT)
Received: by canoe.dclg.ca (Postfix, from userid 101)
	id C70741D1C83; Tue,  3 Aug 2004 11:08:55 -0400 (EDT)
From: David Gilbert <dgilbert@dclg.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16655.43655.686564.873222@canoe.dclg.ca>
Date: Tue, 3 Aug 2004 11:08:55 -0400
To: Tim Kientzle <kientzle@freebsd.org>
In-Reply-To: <410F28E1.8080105@freebsd.org>
References: <410F28E1.8080105@freebsd.org>
X-Mailer: VM 7.17 under 21.5  (beta15) "celery" XEmacs Lucid
cc: freebsd-current@freebsd.org
cc: freebsd-ports@freebsd.org
Subject: HEADS UP: tar -l is now (intentionally) broken.
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2004 15:08:59 -0000

>>>>> "Tim" == Tim Kientzle <kientzle@freebsd.org> writes:

Tim> Since POSIX and GNU violently disagree about the meaning of "tar
Tim> -l", and there seem to be strong adherents to both
Tim> interpretations, I'm preparing to commit a patch that breaks "tar
Tim> -l" for everyone:

Tim> $ tar -cl foo Error: -l has different behaviors in different
Tim> tars.  For the GNU behavior, use --one-file-system instead.  For
Tim> the POSIX behavior, use --check-links instead.

Is this in any way related to the fact that /usr/bin/bsdtar seems
unable (after a new world from yesterday) to archive any files?

[2:1:301]dgilbert@canoe:~> bsdtar -cvf temp .bashrc
a .bashrc: tar format cannot archive this: Inappropriate file type or format

... is what I get.

Dave.

-- 
============================================================================
|David Gilbert, Independent Contractor.       | Two things can only be     |
|Mail:       dave@daveg.ca                    |  equal if and only if they |
|http://daveg.ca                              |   are precisely opposite.  |
=========================================================GLO================