Date: Tue, 20 Aug 2013 08:28:18 +0200 From: Jeremie Le Hen <jlh@FreeBSD.org> To: Eitan Adler <lists@eitanadler.com> Cc: freebsd-current Current <freebsd-current@freebsd.org>, Boris Samorodov <bsam@passap.ru> Subject: Re: bsdtar/libarchive change behaviour 9->10 Message-ID: <20130820062818.GB24767@caravan.chchile.org> In-Reply-To: <CAF6rxgnm6-XPUj8F%2BaAsFiMnd3JymjzxoC-A5yy%2BOeuHvRJitQ@mail.gmail.com> References: <52111AD9.9030001@passap.ru> <164B2B31-D142-4F0A-8FD1-EE112906A470@kientzle.com> <CAF6rxgnm6-XPUj8F%2BaAsFiMnd3JymjzxoC-A5yy%2BOeuHvRJitQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 19, 2013 at 01:52:33AM +0200, Eitan Adler wrote: > On Sun, Aug 18, 2013 at 9:39 PM, Tim Kientzle <tim@kientzle.com> wrote: > > 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). This sounds like a POLA breakage. The rule is maybe different for softwares in contrib/. > > If you are using libarchive directly, you can ask it > > to not interpret those files as metadata. Bsdtar does > > request such handling from libarchive. > > Perhaps this could be exposed to the UI as a env var or a flag? +1 for this. -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130820062818.GB24767>