Date: Mon, 19 Aug 2013 01:52:33 +0200 From: Eitan Adler <lists@eitanadler.com> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-current Current <freebsd-current@freebsd.org>, Boris Samorodov <bsam@passap.ru> Subject: Re: bsdtar/libarchive change behaviour 9->10 Message-ID: <CAF6rxgnm6-XPUj8F%2BaAsFiMnd3JymjzxoC-A5yy%2BOeuHvRJitQ@mail.gmail.com> In-Reply-To: <164B2B31-D142-4F0A-8FD1-EE112906A470@kientzle.com> References: <52111AD9.9030001@passap.ru> <164B2B31-D142-4F0A-8FD1-EE112906A470@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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). Are there other such examples? > 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? -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgnm6-XPUj8F%2BaAsFiMnd3JymjzxoC-A5yy%2BOeuHvRJitQ>