ARJANEN Loïc Jean David
ARJANEN Loïc Jean David
I'm pretty sure it's not possible to port libarchive to be strictly C89 compliant without far too much effort for the reward because libarchive's external identifiers are not only too...
Given the issue noted in issue #80 with determining how is the digest encoded, shouldn't the specification be changed into something like `labelled-digest = algorithm ":" encoding ":" digest-value`? With...
I wish to take up this issue if it's still current.
Sorry I wasn't here, life got in the way. I intend to do it by the first week of January at the latest.
Hello, Has there been any progress on a prototype for that feature? If not, I'd like to take a stab at it in Java.
From what I could find on a search of the respective specifications, the formats libarchive supports which have per-archive comments are PAX, ZIP, Cabinet and RAR5. Of these, only RAR5...
Reading a description of the 7-Zip file format — namely [the one from the py7zr project](https://py7zr.readthedocs.io/en/latest/archive_format.html) — I think that 7-Zip doesn't support per-archive comments but only per-entry ones.
@kientzle could you please check that I'm going in the correct direction API-wise? I'd prefer to get your feedback before embarking on the write support as well as the other...
I split the PR so there should be only the NTFS timestamp field support left in here.
The ZIP specific functions have been moved to the relevant files and their names clarified, the documentation has been changed, and the UT extra data is now written if the...