From owner-freebsd-ports@FreeBSD.ORG Tue Aug 3 18:10:09 2004 Return-Path: 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 7A4E616A4CE; Tue, 3 Aug 2004 18:10:09 +0000 (GMT) Received: from smtp-mclean.mitre.org (smtpproxy2.mitre.org [192.80.55.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id E723E43D58; Tue, 3 Aug 2004 18:10:08 +0000 (GMT) (envelope-from jandrese@mitre.org) Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i73IA8D24416; Tue, 3 Aug 2004 14:10:08 -0400 Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i73IA7424368; Tue, 3 Aug 2004 14:10:07 -0400 Received: from mm112324-2k.mitre.org (128.29.3.51) by mailhub1.mitre.org with SMTP id 8701219; Tue, 03 Aug 2004 14:10:07 -0400 Message-ID: <410FD4FE.4030409@mitre.org> Date: Tue, 03 Aug 2004 14:10:06 -0400 From: Jason Andresen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <410F28E1.8080105@freebsd.org> <20040803072859.GA944@isis.wad.cz> <200408031301.41181.michaelnottebrock@gmx.net> In-Reply-To: <200408031301.41181.michaelnottebrock@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Roman Neuhauser cc: Tim Kientzle cc: freebsd-ports@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2004 18:10:09 -0000 Michael Nottebrock wrote: >On Tuesday 03 August 2004 09:28, Roman Neuhauser wrote: > > > >>>In short, everyone wins on -o, everyone loses >>>on -l. That seems fair. ;-) >>> >>> >> I believe "loses" is the keyword here. >> >> > >You don't loose anything if set POSIXLY_CORRECT > > I'm actually in favor of adding GNULY_CORRECT too, since you occasionally run into self extracting shellscripts and the like that assume GNU behavior (usually when installing Linux apps that come as a giant bash sharchive). I don't think I've ever run into this specific problem, but there is a definate possability and getting those shell scripts to work is hard enough without having some way to override the correct (but incompatable) behaviour. Just my $0.02