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

On Mon, Aug 24, 2026 at 11:35:02AM -0400, Mouse wrote:
> > While the unix-ish interpretation that mouse potinted at is great
> > when using the archive in the same context it was created, it forces
> > other extractors to guess the encoding, which is pretty bad.
> 
> Unix pathnames have historically been octet strings, uninterpreted
> except for slash and NUL.  I would certainly *hope* that they still are
> at the syscall level; anything else is IMO a "renders it unusable" bug.
> Treating filenames as character strings anywhere but user presentation
> leads directly to a large morass of trouble.
> 

Plus, IMHO, that one legitimately expects an archiver to be "lossless"
i.e. it extracts exactly what it has instructed to archive. If there is
any modification (except if explicitely requested so definitively not
by default) or if there is any loss of information, the utility should
not be called an archiver.
-- 
        Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C