From owner-freebsd-current@FreeBSD.ORG Sun Aug 18 19:39:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 48F7894A for ; Sun, 18 Aug 2013 19:39:39 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2633028A4 for ; Sun, 18 Aug 2013 19:39:38 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r7IJdbiW059107; Sun, 18 Aug 2013 19:39:37 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.123] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id wjjc7jpvrfkbww3hcmznvhszr2; Sun, 18 Aug 2013 19:39:37 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: bsdtar/libarchive change behaviour 9->10 Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <52111AD9.9030001@passap.ru> Date: Sun, 18 Aug 2013 12:39:37 -0700 Content-Transfer-Encoding: 7bit Message-Id: <164B2B31-D142-4F0A-8FD1-EE112906A470@kientzle.com> References: <52111AD9.9030001@passap.ru> To: Boris Samorodov X-Mailer: Apple Mail (2.1283) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Aug 2013 19:39:39 -0000 On Aug 18, 2013, at 12:04 PM, Boris Samorodov wrote: > Hi All, > > there are two systems which produce different results: > ----- > % uname -a > FreeBSD int.wart.ru 9.2-BETA2 FreeBSD 9.2-BETA2 #19 r253968: Tue Aug 6 > 04:16:05 SAMT 2013 bsam@int.wart.ru:/usr/obj/usr/src/sys/INT i386 > > % tar --version > bsdtar 2.8.5 - libarchive 2.8.5 > > % tar -tf /usr/ports/distfiles/Catalyst-Plugin-Prototype-1.33.tar.gz | > grep Plugin/ > Catalyst-Plugin-Prototype-1.33/lib/Catalyst/Plugin/ > Catalyst-Plugin-Prototype-1.33/lib/Catalyst/Plugin/._Prototype.pm > Catalyst-Plugin-Prototype-1.33/lib/Catalyst/Plugin/Prototype.pm > ----- > % uname -a > FreeBSD srv.bb.tel.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #7 r253953: Mon > Aug 5 16:16:42 SAMT 2013 > bsam@srv.bb.tel.ru:/usr/obj/usr/src/sys/BB64X amd64 > > % tar --version > bsdtar 3.1.2 - libarchive 3.1.2 > > % tar -tf /usr/ports/distfiles/Catalyst-Plugin-Prototype-1.33.tar.gz | > grep Plugin/ > Catalyst-Plugin-Prototype-1.33/lib/Catalyst/Plugin/ > Catalyst-Plugin-Prototype-1.33/lib/Catalyst/Plugin/Prototype.pm > ----- > > I.e. the CURRENT system does not honor the presence of "._*" file. > The file seems to be a MAC file and anyway get deletted before > installation. > > So, the question is: is it a regression/bug/new feature? Libarchive 3 does handle ._* files differently than libarchive 2. In libarchive 2.x those files were treated as normal files and bsdtar then had special code to process them as Mac extensions. Libarchive 3.x can treat them as extended metadata. As a result, bsdtar doesn't see them at all (except as additional metadata which can't be restored on FreeBSD). If you are using libarchive directly, you can ask it to not interpret those files as metadata. Bsdtar does request such handling from libarchive. Tim