You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the archives always seemed to be using the 7z packaging regardless of what I specified saving the archive as (e.g. .zip, .bzip, .tar, etc.). I implemented a basic switch that correctly infers the archive format based on the archive extension - the ArchiveFormat flag can still be used as an override, but otherwise seems unnecessary and this reduced instances where the flag isn't passed and other extraction utilities think they have a .tar.gz but are in fact needing to decompress a 7z archive which they may be unable to handle correctly.
Quick and dirty implementation, but worked in my fork;
I like the idea. I think I'll introduce a new enum for the output format with the same members as OutArchiveFormat plus Auto. If Auto is passed (which would be the default), it would try to infer the format from the archive file name, otherwise as specified.
I noticed that the archives always seemed to be using the 7z packaging regardless of what I specified saving the archive as (e.g. .zip, .bzip, .tar, etc.). I implemented a basic switch that correctly infers the archive format based on the archive extension - the ArchiveFormat flag can still be used as an override, but otherwise seems unnecessary and this reduced instances where the flag isn't passed and other extraction utilities think they have a .tar.gz but are in fact needing to decompress a 7z archive which they may be unable to handle correctly.
Quick and dirty implementation, but worked in my fork;
The text was updated successfully, but these errors were encountered: