Re: CVS commit: src/external/bsd/libarchive/dist/libarchive

Martin Husemann <[email protected]> writes:

> On Mon, Aug 24, 2026 at 02:55:06PM +0200, Thomas Klausner wrote:
>> Personally I'm not quite sure if I want a tar tool to convert between
>> encodings. Is the base encoding included in the tar file?
>
> Officially (AFAICT) ustar format only supports ASCII, everything else
> is a grey area.

I can see that, tar being from long ago.  Within UB, though, it seems
really obvious to just take the bytes in the filename in the archive and
use that with syscalls and not do any character set stuff, unless
explicitly requested.

What kind of conversions do you think are happening with libarchive, and
why do you think those conversions are a good idea?  (Genuine question;
I am fuzzy about beyond-ascii in filenames in general)



> Best option is to use pax format, where the filename is guaranteed to
> be UTF8 encoded.


That's not a question on the table - this is about dealing with tar
files others create.